Imo separating those is more annoying to work with in many corner cases and makes little improvement
Imo separating those is more annoying to work with in many corner cases and makes little improvement for the other cases
Euclidean vector, yesColor in System.NumericsNormalize, which trends towards 0 for integersColor class doesn't use a packed value, it stores float R, G, B, and A valuesPoint(2<int>, idk) return a Vector on subtraction, and then that way the difference is clear (like DateTime and Timespan Vector2<int> because it loses dataPow for integers, it is fundamentally lossy and ill suited for most needsVector2<float> and do the conversionsT in, T out and represent the concepts in a way that works well for the common needsEuclidean vectorColorColorNormalize0Point(2<int>, idk)Vector2<int>PowVector2<float>T in, T out