[GHC] #8823: showFloat for higher precision types produces strange results for some values

[GHC]

#8823: showFloat for higher precision types produces strange results for some
values
------------------------------------------------+--------------------------
        Reporter:  axman6                       |            Owner:
            Type:  bug                          |           Status:  closed
        Priority:  low                          |        Milestone:
       Component:  Prelude                      |          Version:
      Resolution:  invalid                      |  7.8.1-rc1
Operating System:  Unknown/Multiple             |         Keywords:
 Type of failure:  Incorrect result at runtime  |     Architecture:
       Test Case:                               |  Unknown/Multiple
        Blocking:                               |       Difficulty:
                                                |  Unknown
                                                |       Blocked By:
                                                |  Related Tickets:
------------------------------------------------+--------------------------

Comment (by axman6):

 Hmmm, it seems you're right, but nonetheless my implementation of
 decodeFloat is the only one that makes sense for my type since it can
 represent more than 212 bits of data (for example 1.0000000...005 is
 represented with the doubles 1.0 and 0.5eN,  and 0 for the two other
 doubles]). It seems that perhaps in my case I may need floatDigits to be
 very large indeed or use another method to show the number.

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