"Ch. A. Herrmann" <[EMAIL PROTECTED]> writes: > that's true, of course. Furthermore, aside from "x==x", optimizations > could deal with "x-x", "x && (not x)" and many other expressions. > > Concerning "safety". As far as I can see there is only a single reason: > Partially correct programs terminate more often. Doesn't > that meet the philosophy behind laziness? If you're using ghc extensions, you could be relying on an exception thrown by x==x. Carl Witty
- 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
- Carl R. Witty