>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. I imagine expressions like x==x could appear as the result of transformations in program specialisation, like specialising f x x where f x y = if x==y then .... Replacing x==x with True is of course still unsafe in Haskell, for the reasons already pointed out. Björn Lisper
- 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