[GHC] #5129: "evaluate" optimized away

[GHC]

#5129: "evaluate" optimized away
---------------------------------+------------------------------------------
    Reporter:  dons              |        Owner:  simonmar                   
        Type:  bug               |       Status:  new                        
    Priority:  normal            |    Milestone:                             
   Component:  Compiler          |      Version:  7.0.3                      
    Keywords:  seq, evaluate     |     Testcase:                             
   Blockedby:                    |   Difficulty:                             
          Os:  Unknown/Multiple  |     Blocking:                             
Architecture:  Unknown/Multiple  |      Failure:  Incorrect result at runtime
---------------------------------+------------------------------------------

Comment(by rl):

 Why is {{{x `seq` return ()}}} discouraged? Why would I use `evaluate` if
 I want to make my code strict in `x` but don't care when it is evaluated?
 This seems to be what ezyang's examples are about (the ones in
 `Foreign.C.String` even say so explicitly) so I don't understand why these
 should be replaced with `evaluate`.

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