-
Notifications
You must be signed in to change notification settings - Fork 62
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
Make ArrayPartition default instead of ProductRepr #612
Conversation
Codecov Report
@@ Coverage Diff @@
## master #612 +/- ##
=======================================
Coverage 99.00% 99.00%
=======================================
Files 104 104
Lines 10039 10047 +8
=======================================
+ Hits 9939 9947 +8
Misses 100 100
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
How breaking this is is maybe hard to estimate? And we could also deprecate ProductRepr? |
We could. Probably the biggest benefit would be reducing testing time in Manifolds 0.9 (when it would be removed). |
You changed quite some code for the switch, so a default data type might be helpful in case we want to switch again? I think in favour of ArrayPartition we should deprecate ProductRepr (and remove it in 0.9), since I do not see much gain in inventing our own data type if probably better tested and maybe more efficient others do exist. |
Most code changes is either adapting tests or adding some missing functionality to I guess the only way to switch defaults would be encoding it in the manifold?
|
I just feel it is maybe a bit beyond what Manifolds.jl should provide, if it exists - unless there is a really good reason for ProductRepr. The printing could be a PR to the original package then? |
That's exactly the direction we are going in here -- removing ProductRepr from Manifolds.jl.
Maybe I'll try then. |
@kellertuer I think this is ready 🙂 |
I remember reworking Circle some time ago to make it accept one-element vectors as points and tangent vectors but the current implementation is a bit conflicted about it. |
I hope we did not loose any of these in merges? I had in mind Circle works for both, yes. |
It was a bit incorrect but I haven't checked git blame to see why. |
Resolves one of the issues raised in #609 .
This should be only slightly breaking so I don't think an actual breaking release is necessary.