-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Renaming functions / API redesign for v1.0 #102
Comments
Personally, I would love to test the symbolical support of fully general metric tensor . Is there any doc or specific commits that I can check? |
That's been planned for the next release v0.9, I've been saving the fully general metric tensor as the last step for various reasons related to the order of features in which I want to design the package. I am currently working on several commits for the general metric tensor and symbolic computation with it, but it's a work in progress and I won't be committing it until I settle on a design. Unfortunately, I also lost some work in progress when my SSD died a few months back, but I will recover from it. |
@utensil arbitrary @basis MetricTensor([0 -1 0; -1 0 0; 0 0 1]) |
There will be another v0.9 release, followed by a 1.0 release of
Grassmann
in the future. In the v0.9 to v1.0 transition is the final opportunity to make internal breaking changes with regards to renaming functions / API redesign.Does anyone wish to contribute specific comments about a v0.9/v1.0 redesign for
Grassmann
API and renaming some functions?The text was updated successfully, but these errors were encountered: