John Hughes <[EMAIL PROTECTED]> writes: > As far as the power of the optimizer is concerned, my guess is programmers > very rarely write x==x (unless they MEAN to force x!), so the loss of > optimization doesn't matter. Of course, in principle, an optimizer *could* > replace x==x by x`seq`True (if x is known to be of base type), and the x`seq` > might well be removed by later transformations (if x can be shown to be > defined, something compilers do analyses to discover). Who knows, maybe this > happens in the innards of ghc... Or the compiler could internally create its own HyperStrict class and replace x==x by x`hyperSeq`True, if all the Eq instances involved in the type of x are known to be reflexive (which is the case if they were all automatically derived). :-) Carl Witty
- RE: How to force evaluation entirely? Simon Peyton-Jones
- RE: How to force evaluation entirely? John Hughes
- RE: How to force evaluation entirely? Ch. A. Herrmann
- RE: How to force evaluation entirely? Patrik Jansson
- Re: How to force evaluation entirely? Lennart Augustsson
- Re: How to force evaluation entirely? Fergus Henderson
- RE: How to force evaluation entirely? John Hughes
- Re: How to force evaluation entirely? Marcin 'Qrczak' Kowalczyk
- Re: How to force evaluation entirely? Bjorn Lisper
- Re: How to force evaluation entirely? Carl R. Witty
- Re: How to force evaluation entirely? Michael Marte
- Re: How to force evaluation entirely? Zhanyong Wan
- Re: How to force evaluation entirely? Ch. A. Herrmann
- Re: How to force evaluation entirely? Ch. A. Herrmann
- Re: How to force evaluation entirely? Carl R. Witty