Bulat Ziganshin wrote:
But in a world passing interpretation of IO, print is supposed to be a
pure Haskell function. So the value world2 can only depend on the values
of print and world1, but not on the actions of some concurrent thread.
the whole World includes any concurrent thread though ;)
Oh I see. So given world1, print can simulate the behavior of the
concurrent thread to take it into account when constructing world2.
Since that simulation depends only on world1, print is still pure.
Does that mean that world passing *does* account for concurrency after all?
Tillmann
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
