Replies: 4 comments 2 replies
-
💯 agreed! Can we do these as aliases and then deprecate the old naming over time? |
Beta Was this translation helpful? Give feedback.
2 replies
-
and probably always keep the aliases: const Position2 = Position{2} |
Beta Was this translation helpful? Give feedback.
0 replies
-
Just adding technical detail: getManifold(::Position{N}) where N = Manifolds.TranslationGroup(N) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Scalar is a good generic name for me for applications that aren't spatial. I like |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Why not consolidate:
IIF.ContinuousScalar == Position1 == Position{1}
RoME.Point2 == Position2 == Position{2}
RoME.Point3 == Position3 == Position{3}
RoME.Point2
andRoME.Point3
already have name conflicts with JuliaGeometry.ContinuousScalar
seems out on its own.Added benefit is users can then happily build higher dimensional stuff with
Position{4}
, etc. It's then very likely that many use cases fall underManifolds.TranslationGroup(N)
andIIF.Position{N}
.Beta Was this translation helpful? Give feedback.
All reactions