do i have to write the API specification for all like 8 types?
do i have to write the API specification for all like 8 types?
KSorry I haven't looked yet, but from what's said here I gather that it returns float always?
Mno, it returns whatever type you want
Mvec.Length<TFloat>()
Ppoint out the differences between the types, but other than that no.
KTFloat = sbyte?
Ptechnically you don't even have to write the type specs which is something i'm abusing in the SilkTouchX proposal to leave things open for the team to change
Mthat would be a not very useful length method
Mdoes sbyte implement IRootFunctions
Mif not, not possible
KFair, Length squared is totally possible though?
Mi wrote them because you asked!
Mlengthsquared is not constrained
KYes it'll likely overflow and isn't super common, but eh
Mit's just INumber
Poh yeah, and for maths we definitely want them
Pbut you don't need to do one for every type
Plike for a typespec for Vector4 you can do
Pas long as your intent is clear, it can be approved
Mso yes you can do LengthSquared<sbyte>
KDon't want to bother you about it given I haven't read the proposal but then I don't understand what perksey is saying here
Mme neither
Myou monster /j
K@shrimpcat in the utf8 formatting bit, why not also check the output from the .Append bits to return early? unless im misremembering those method's return values
Mthey return false
Mtahts why the &&
Kyeah but why discarding the whole is i guess my question
Kim probably just being slow to process this whole setup though
Mbecause you can't have a bunch of && as a statement
Pif we can implement something in terms of the generic maths interfaces without implementing the functions exposed by any of the generic maths interfaces ourselves (a la Scalar.BaseOps) then i'm happy with it being in Silk.NET.Maths
Mand Utf8.TryWrite checks itself
Mif i added a check there, it would be a duplicate
M
Mthis is definitely going way over my head
Pthat's about as clear as i can make it
Kah ok cool
Mkai if you understand what he means, please explain it to me in baby words
Kstatic T LengthSquared<T>(this Vector3<T> vec) where T : INumber<T>, IFloatingPoint<T>;
???
???
Mthere is more than one of those!
Mcheck Vector3<T>
Mpublic readonly TReturn LengthSquared<TReturn>() where TReturn : INumber<TReturn>Kyeah
Mthis is an instance method (but it can be an extension method)
Kits a shortcut where TReturn and T are the same
Pbasically if ever we find ourselves constrained by the generic maths constraints, then we probably shouldn't be working to allow whatever you're trying to do
Mhm.
Mwhat is that comment about, though?
KI don't really get why there's two?
Why is the one without a return arg restricted to floating point? Seems like extra typing for user for nothing?
Why is the one without a return arg restricted to floating point? Seems like extra typing for user for nothing?
Mbecause there is no use of calling Length<T> if the result is not a decimal
Kthe one without a result is a shortcut if T is already floating
Kand you just want to use that
