[GHC] #9530: min / max do not always return a NaN when one of the arguments is NaN

[GHC]

#9530: min / max do not always return a NaN when one of the arguments is NaN
-------------------------------------+-------------------------------------
              Reporter:  jrp         |            Owner:
                  Type:  bug         |           Status:  closed
              Priority:  normal      |        Milestone:
             Component:  Prelude     |          Version:  7.8.3
            Resolution:  invalid     |         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 carter):

 the ieee min/max  behavior on nans is bonkers and useless for us.

 @dfeuer happy to chat about this more via irc or email, but Floats aren't
 numbers, they just act like they are, but explaining their semantics in
 more detail and why/when ieee should be ignored or not is too complicated
 for trac tickets

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/9530#comment:4>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler