On Thu, Feb 5, 2009 at 8:20 PM, ChrisK <haskell@list.mightyreason.com> wrote:

Since this is strict there is no laziness and the code must evaluate the input and output "State RealWorld" to ensure they are not bottom or error.

Interesting. I also thought it was the passing of the RealWorld that caused the sequencing, I never realized that the strictness played an important role here. 

So what would happen if it would be lazy instead of strict? What kind of craziness would occur?