We have to assume undef could be an snan, which would need quieting so
returning qnan is safer than undef. Also consider strictfp, and don't
care if the result rounded.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
We have to assume undef could be an snan, which would need quieting so returning qnan is safer than undef.
So you've chosen to optimize assuming that an undef input was a nan. Is that better than assuming it was something more ordinary like 0?
Comment Actions
qnan matches the current fdiv handling. nan also enables folding out more use operations more consistently