[Haskell] threading mutable state through callbacks

[Vincenzo Ciancia]

On Tuesday 12 October 2004 12:23, Adrian Hey wrote:
>  I don't know what more
> general-purpose extension you have in mind, but couldn't you just
> borrow from do syntax at the top level

I think that the problem is with the order of execution of these 
bindings. For example ghci supports top-level "let x <- something" 
declarations, but the haskell compiler does not have to respect any 
order of execution, which would instead be forced. The general purpose 
extension could however require the same proof obligations of 
unsafeInterleaveIO, but how do we deal with

x <- someAction
y <- someAction(x)

V.

-- 
Bow down before the one you serve,
you're going to get what you deserve.
[Nine Inch Nails]