Re: [Haskell-cafe] shared oneShot IO (was top-level state proposals)

2007-05-29 Thread Dan Weston
I was wondering why, since IO is an instance of MonadFix [1], and therefore of ArrowLoop (Kleisli m), and since The loop operator expresses computations in which an output value is fed back as input, even though the computation occurs only once. [2], the MonadFix or ArrowLoop class (through

Re: [Haskell-cafe] shared oneShot IO (was top-level state proposals)

2007-05-29 Thread Claus Reinke
I was wondering why, since IO is an instance of MonadFix [1], and therefore of ArrowLoop (Kleisli m), and since The loop operator expresses computations in which an output value is fed back as input, even though the computation occurs only once. [2], the MonadFix or ArrowLoop class (through

[Haskell-cafe] shared oneShot IO (was top-level state proposals)

2007-05-26 Thread Claus Reinke
i thought the discussion had actually progressed a little further than might be obvious from http://www.haskell.org/haskellwiki/Top_level_mutable_state here is my summary of what i thought was the state of the discussion, followed by a hopefully simpler proposal. first, i'd like to