> If you don't deem it too late to change that, I'd suggest renaming as perhaps invFull()?
Sounds like a good idea! I will try to change that (and add a real accurate) soon. Note that in all cases, if the value cannot be represented in the destination type well, you are done for… If find a bit fun that division are the only operations which lose precision in fixed point math!
I think now is the time for these kind of things, I think I used one or two invAccurate in Mozzi (where speed is usually more important than precision) that can easily be changed into invFull
Sounds like a good idea! I will try to change that (and add a real accurate) soon. Note that in all cases, if the value cannot be represented in the destination type well, you are done for… If find a bit fun that division are the only operations which lose precision in fixed point math! I think now is the time for these kind of things, I think I used one or two
invAccuratein Mozzi (where speed is usually more important than precision) that can easily be changed intoinvFull_Originally posted by @tomcombriat in https://github.com/tomcombriat/FixMath/pull/4#discussion_r1542110046_