-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET Framework version can be reduced to v4.0 #31
Comments
I just had a quick look at the usage of this and it appears to only be used internally. If that's correct it's probably best just to return the plain array and trust that the consumer isn't going to misbehave (i.e. mutate the array).
This is the more annoying one - a vector type which is incompatible with everyone else is pretty useless! Is it possible to install the System.Numerics library and use it from .net4.0?
If it can be done in an ergonomic way I think it's a pretty cool idea. I'll be very happy to accept PRs :) Actually this also gives me an interesting idea: I wonder what it would take to support .net core? That would give us support on a tonne of platforms. |
Yes, all the usages of The I'll try to make a pull request in several days when I'm free. Thank you for the reply. Cheers! |
I used For .NET Core, there are a lot of type checks (especially |
I'm working on a project which uses .NET Framework 4.0. I tried to install SupersonicSound via NuGet and received a 'Not supported' error. So I checked the source code and found out this solution uses .NET Framework 4.6.
I try to build SupersonicSound under v4.0 and there are errors:
IReadOnlyList
(introduced in v4.5) andVector3
(usingSystem.Numerics
, this assembly has a v4.0 version but the type was introduced in v4.6).Since v4.0 is pre-installed in Windows 7 and it is forward-compatible, I think if SupersonicSound can run under v4.0 it can be more widely used. To achieve this, I suggest writing our own implementation for
IReadOnlyList
(which is only used on arrays in this solution) andVector3
.What do you think?
The text was updated successfully, but these errors were encountered: