RE: awaitEval in Concurrent Haskell

Does this mean you can womble along with Claus's suggestion? I'm feeling a bit swamped at the moment, and not keen to undertake another open-ended implementation exercise. So if you can manage without, and perhaps use the experience to refine the specification of a Really Useful Feature, that'd be great from my point of view. Simon | -----Original Message----- | From: Colin Runciman [mailto:colin@cs.york.ac.uk] | Sent: 17 February 2003 13:40 | To: Claus Reinke | Cc: Colin Runciman; C.Reinke; Simon Peyton-Jones; GHC users | Subject: Re: awaitEval in Concurrent Haskell | | A couple of hours ago, I wrote (in reponse to Claus Reinke's suggestion): | | > Thanks for this further suggestion. A solution along these lines | > might be | > possible, but it would still be restricted ... | | Actually a mild variant of Claus's proposal seems to work out | quite well. Another way to avoid the problems with types is | to use a multi-parameter type class. Little example attached. | | So, thanks again Claus! | | Regards | Colin R

Simon,
Does this mean you can womble along with Claus's suggestion? I'm feeling a bit swamped at the moment, and not keen to undertake another open-ended implementation exercise. So if you can manage without, and perhaps use the experience to refine the specification of a Really Useful Feature, that'd be great from my point of view.
Yes, I think that's a reasonable way to go. So stand easy :-) .... Colin R
participants (2)
-
Colin Runciman
-
Simon Peyton-Jones