sjoerd at w3future.com
Tue Jul 3 19:53:00 CEST 2012
Did you check the implementation of "empty"? I didn't really think that one through, it was just the first thing I tried and it seemed to work. I would not be surprised if there's a better way to wait forever.
On Jul 3, 2012, at 3:33 PM, Simon Marlow wrote:
> Thanks, I've incorporated your Concurrently type, and renamed doConcurrently to mapConcurrently (by analogy with mapM).
> I released async-220.127.116.11 with the latest round of changes:
> Changes in 18.104.22.168:
> Added a Functor instance for Async
> Added asyncBound, asyncOn, asyncWithUnmask, asyncOnWithUnmask, withAsyncBound, withAsyncOn, withAsyncWithUnmask, withAsyncOnWithUnmask.
> Added mapConcurrently
> Added Concurrently (with Applicative and Alternative instances)
More information about the Libraries