Kinda sniped by 1. here. I always wanted to have the ability to have ops have the ability to have a storage precision and each op have a specified precision. Iirc there's lots of gains to have.
this stance does fundamentally change the proposal, and as much as i have agreed in the past, given that we have strict rules codified in the BCL now in the form of the generic maths interfaces, it makes sense to follow them given they're the stewards of the ecosystem
technically 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
@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
if 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