On Fri, Feb 03, 2006 at 10:20:01AM +0100, Tomasz Zielonka wrote: > Even if concurrency is part of Haskell', it should still be clear > that it doesn't affect the definition of non-concurrent Haskell' subset > at all (is that true?). For example, all pure functions will be entirely > thread-safe.
As another example, Ben Rudiak-Gould recently pointed out that the inclusion of stToIO breaks threaded state reasoning for ST, e.g. readSTRef won't necessarily get what your last writeSTRef wrote (because the region might be RealWorld, with other threads modifying it). _______________________________________________ Haskell-prime mailing list Haskell-prime@haskell.org http://haskell.org/mailman/listinfo/haskell-prime
