Christoph Ruegg

Ah, that's supported just fine. I've just closed #161 with a fix.

- .Net Standard 2.0 is only usable from 4.6.1 and newer, with workarounds (otherwise 4.7.1 and newer) - .Net Standard 1.3 is only usable from 4.6 and newer and is...

Or would we want to leverage new APIs only available in 4.7.1?

@JohanLarsson are you aware of any users targeting .Net Framework < 4.6? What about < 4.7.1?

FYI: I've dropped support for older platforms and upgraded the target frameworks to .NET Framework 4.6.1 and .NET Standard 2.0.

Yes, I'd expect a `Matrix3D` as well, in both cases.

Yes, and it requires installing previews and enabling them by registry settings. I expect the SIMD vectors work on the current platform as well, but of course not vectorized and...

Just to clarify, I'm happy with the current very direct struct + public readonly fields approach. I do not suggest to change them.

I don't see a problem with the reference as is, in fact I'd even suggest to add a few more routines to convert between the data structures of both of...

Just for the record, automatic simplification to a well-defined standard form is common practice and massively simplifies code almost everywhere if you can safely assume it always has standard structure....