#9530: min / max do not always return the other argument when one of the arguments
is NaN
-------------------------------------+-------------------------------------
Reporter: jrp | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Prelude | Version: 7.8.3
Resolution: | Keywords:
Operating System: MacOS X | Architecture: Unknown/Multiple
Type of failure: Incorrect | Difficulty: Easy (less than 1
result at runtime | hour)
Test Case: | Blocked By: 9276
Blocking: | Related Tickets: 9276
Differential Revisions: |
-------------------------------------+-------------------------------------
Comment (by jrp):
Thanks. I'll have a more detailed look. I can't, however, see any good
reason for having min / max asymmetrical in their arguments, whether the
result is to be NaN or the other argument.
The standard seems to agree. It says (at 5.3.1) that
'''''minNum(x, y) is''' the canonicalized number x if x