mathnet-spatial
mathnet-spatial copied to clipboard
mathnet
What is outstanding for 1.0.0?
Its not clear what is in the way of bringing mathnet-spatial out of pre-release status. I'm using it in a couple projects at the moment, and am presonally quite satisfied with it.
If I had insight into what is holding back rolling over to v1.0.0, I might be inclined to help take down some issues.
CoordinateSystem should be rewritten as struct for performance, the current implementation is likely pretty slow. The entire API around coordinate system should be improved.
Originally I wrote it to have a similar API to the coordinate system class in Autodesk Invetor. I remember that I have not been happy with it at all.
Also we should try to add some more documentation for methods, help from a native speaker would be greatly appreciated.
That is just from the top of my head not having used spatial much the last two years or so.
I've dropped the prerelease marker for the v0.3.0 release, so it is no longer technically a prerelease (although by convention 0.x versions are still exempt from some strict semantic versioning rules).
Thanks!
All's fair in love and 0.x.x
Jules
On Nov 5, 2016, at 3:01 PM, Johan Larsson <[email protected]mailto:[email protected]> wrote:
Perfect!
You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/mathnet/mathnet-spatial/issues/48#issuecomment-258640325, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQ8zjruRwTd5gvEnDET8dTBpCq0CRN5uks5q7O5xgaJpZM4KfIRd.