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

[GHC]

#9530: min / max do not always return the other argument 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:              |
-------------------------------------+-------------------------------------
Changes (by rwbarton):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Replying to [comment:3 dfeuer]:
 > I think it probably makes sense to have multiple sets of operations
 available:
 >
 > 1. IEEE compliant stuff, whether sane or not.
 >
 > 2. Stuff that's fast in hardware, whether sane or not.
 >
 > 3. Stuff that's sane.

 I whole-heartedly agree with this, but, (at most?!) one of these behaviors
 can be the behavior of the `Ord Double` instance.

 Any proposed change to that instance needs to be made through the library
 submissions process, so I'm going to close this ticket as "invalid". This
 discussion should continue, though! Maybe here, or perhaps on a new wiki
 page—there are getting to be a number of these tickets on floating-point
 behavior and it would be good to have all the discussion in one place.

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