#3744: Comparisons against minBound/maxBound not optimised ---------------------------------+------------------------------------------ Reporter: rl | Owner: Type: bug | Status: new Priority: normal | Milestone: 7.0.1 Component: Compiler | Version: 6.13 Keywords: | Testcase: Blockedby: | Difficulty: Os: Unknown/Multiple | Blocking: Architecture: Unknown/Multiple | Failure: Runtime performance bug ---------------------------------+------------------------------------------
Comment(by rl): I don't think these rules would work reliably because the comparison operators could (and would) be inlined before the rules have had a chance to fire. Rules for specific primitive types wouldn't have this problem but IIRC, matching against the actual bounds literals can be problematic. -- Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3744#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