To describe unit quantities with dimension [length], I initially named this class Position. I think I was working on the Stage class, so it made sense then. However, most of the time when we need units of this dimension we're not really talking about absolute position, but rather some relative length measurement. For instance pixel_size, frame_height--these really aren't "positions" in any sense.
To remedy this, we could
- change
units.Position -> units.Length throughout
- retain
units.Position and make an additional units.Length class that's just an alias of units.Position. Then users can choose which descriptor makes most sense.
Option 1 is easy, but we may lose some type descriptiveness for quantities that truly are positions
Option 2 seems to make redundant code
To describe unit quantities with dimension [length], I initially named this class
Position. I think I was working on theStageclass, so it made sense then. However, most of the time when we need units of this dimension we're not really talking about absolute position, but rather some relative length measurement. For instancepixel_size,frame_height--these really aren't "positions" in any sense.To remedy this, we could
units.Position->units.Lengththroughoutunits.Positionand make an additionalunits.Lengthclass that's just an alias ofunits.Position. Then users can choose which descriptor makes most sense.Option 1 is easy, but we may lose some type descriptiveness for quantities that truly are positions
Option 2 seems to make redundant code