You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I feel like having the x, y, and now, rho and theta getters/setters as part of BaseVector is a bit counter-intuitive. Maybe having the BaseVector as a generic n-dimensional vector (that is also instantiable) that only has operations that work independently of the dimensionality - like it mostly is currently - could be useful.
It might even be possible to move (part of) the constructor to the BaseVector and make it easier for users to implement 4d vectors for example.
(And maybe it's even possible to merge the BaseVector and BaseVectorArray? I might be missing something - I'm pretty new to the codebase - but if it's possible it would remove a lot of code duplication)
The text was updated successfully, but these errors were encountered:
From @Evelyn-H (see #34):
The text was updated successfully, but these errors were encountered: