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
Not sure If I'm misunderstanding something, but shouldn't this try and preserve the unit?.
It's easy enough to handle, in your own code, but I did like the strong types this library provided.
The text was updated successfully, but these errors were encountered:
btrepp
changed the title
Vector2D<T,U>::length should return Length<T,U>
Should Vector2D<T,U>::length() return Length<T,U>
Jan 23, 2020
In practice we found out that people often don't use the units much when dealing with the scalar values (while they do with vectors and other types), so we want to have the default set of common accessors like x,y,length work with raw scalars. We even had *_typed() equivalents for all methods that return scalars but it was apparently too cumbersome to be used in practice so they were removed a little while ago.
I'm keen on adding them back with a less awkward naming scheme, for example get_length(&self) -> Length<T, U>, get_x(&self) -> Length<T, U>, etc. See also #388.
Not sure If I'm misunderstanding something, but shouldn't this try and preserve the unit?.
It's easy enough to handle, in your own code, but I did like the strong types this library provided.
The text was updated successfully, but these errors were encountered: