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
The current solution for units has some capabilities for supporting high-performance conversions and type safety. However, a few aspects of the current solution create friction around automated conversion:
the core capability of unit types, "convert", does not come from a trait, so it cannot be abstracted over
state variables are accessed through the StateModel as Distance, Time, etc newtypes, which was intended to add type safety, but instead makes it challenging to abstract over, and duplicates the choice of having strongly typed unit types like DistanceUnit, TimeUnit, etc
unit types are disjoint, so it is complicated to abstract over all unit types
The text was updated successfully, but these errors were encountered:
The current solution for units has some capabilities for supporting high-performance conversions and type safety. However, a few aspects of the current solution create friction around automated conversion:
Distance
,Time
, etc newtypes, which was intended to add type safety, but instead makes it challenging to abstract over, and duplicates the choice of having strongly typed unit types likeDistanceUnit
,TimeUnit
, etcThe text was updated successfully, but these errors were encountered: