
16 Jan
2025
16 Jan
'25
6:42 p.m.
IEEE floating point doesn't have undefined behavior, so it's always "safe" in the "no undefined behavior" sense. (Assuming that floating point exceptions are disabled. When they are enabled, it's not so clear.)
In that since there's little to be done here too. We'll never set anything that can be queried by std::fetestexcept (since internally it's all integer maths), and I don't think we gain anything by calling std::feraiseexcept with the right arguments, because we'll have to add a bunch of workarounds to keep constexpr. More importantly there's not a lot of support and even fewer people that care. Matt