#3070: floor(0/0) should not be defined
---------------------------------+------------------------------------------
Reporter: carette | Owner: squadette
Type: bug | Status: new
Priority: normal | Milestone: 6.12.1
Component: Prelude | Version: 6.10.1
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Os: Unknown/Multiple
Architecture: Unknown/Multiple |
---------------------------------+------------------------------------------
Comment (by squadette):
Well, it seems like this whole idea of correctness really contradicts some
folks' expectations about speed:
http://hackage.haskell.org/trac/ghc/ticket/2271
http://hackage.haskell.org/trac/ghc/ticket/1434 ("This is really a problem
for me when doing signal processing, since for writing to a common audio
file format or listening to a signal data has to be converted from Double
to Int16.")
http://hackage.haskell.org/trac/ghc/ticket/2281
If we add even more specializations for primitive types, what will happen
to correctness?
Haskell 98 seems to ignore the question of invalid floating point
arguments, however recognizing the existence of NaNs :)
Maybe we should just explicitly state somewhere that we sacrifice
correctness to speed wrt Float <-> Int domain discrepancies.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3070#comment:4>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
