3 ms·
> So yes, that means that you become responsible to either guarantee that erroneous results do not matter or that you will take care to always check the ranges
by celrod 5y ago
> So yes, that means that you become responsible to either guarantee that erroneous results do not matter or that you will take care to always check the ranges of input operands, as "okl" has already posted, to ensure that no overflows, underflows or undefined operations will happen.
This is why I dislike the fact that it removes simple methods for checking if values are NaN, for example.
I do not find it ergonomic to disable these checks.
- kazinator 5y agoIf NaN and Inf values can still happen, but you don't have reliable ways of working with them, that is poor. I think what people really want is a sane floating point mode that throws exceptions instead of these Inf and NaN things, so if their program isn't debugged, they get a clear signal by way of its abnormal termination.