P
V
Sin on a byte).
Quoted by perksey#0000
T
TVector2<T> supporting only floating-point vs supporting integers in general is something I've struggled with finding the right balance for/aroundTTSin(x) for an integer to work much as x / y doesSin(x) for floating-point, as you can say that Pi can be loosely representedTVector2<T> should only be where T : IFloatingPoint<T> (or IFloatingPointIeee754<T>)Point2<T>Tdistance between two points where-as that can be made to makes senseTPTvectorpoint are "the same thing"TPPPPTLength or NormalizationPT.Length or need an extension called .Length()Length was not universally availableTVector2<int> almost means that what you have isn't a vectorT(1, 3) and a vector (1, 3). You have conceptually the "same thing", but also not(0, 0)TDateTime (point) and TimeSpan (vector) in that regardPPPPTPTalso imo a user wanting to use a vector type with a scalar type that fundamentally cannot represent the vector rules is kind of down to them hahaThe issue is in how it restricts our ability to version the types over time. Can we successful expose an API like
Hypot or DegreesToRadians 5 years after it ships, for exampleTTPP
K
M
AM
byte should just be a cast to float, get the sine, then cast back to byteAMAAMAAAAMMAthen cast back to bytei did not initially gather that from what you said here
SinbytebyteVector2<T>Vector2<T>Sin(x)Sin(x)x / yPiwhere T : IFloatingPoint<T>IFloatingPointIeee754<T>Point2<T>distance between two pointspointLengthLengthNormalization.Length.Length()Vector2<int>(1, 3)(1, 3)(0, 0)DateTimeTimeSpanHypotDegreesToRadians