Unlifted async.

Since: 0.1.0.0

Unlifted asyncBound.

Since: 0.1.0.0

Unlifted asyncOn.

Since: 0.1.0.0

Unlifted asyncWithUnmask.

Since: 0.1.0.0

Unlifted asyncOnWithUnmask.

Since: 0.1.0.0

Unlifted withAsync.

Since: 0.1.0.0

Unlifted withAsyncBound.

Since: 0.1.0.0

Unlifted withAsyncOn.

Since: 0.1.0.0

Unlifted withAsyncWithUnmask.

Since: 0.1.0.0

Unlifted withAsyncOnWithMask.

Since: 0.1.0.0

Lifted wait.

Since: 0.1.0.0

Lifted poll.

Since: 0.1.0.0

Lifted waitCatch.

Since: 0.1.0.0

Lifted cancel.

Since: 0.1.0.0

Lifted uninterruptibleCancel.

Since: 0.1.0.0

Lifted cancelWith. Additionally uses toAsyncException to ensure async exception safety.

Since: 0.1.0.0

Lifted waitAny.

Since: 0.1.0.0

Lifted waitAnyCatch.

Since: 0.1.0.0

Lifted waitAnyCancel.

Since: 0.1.0.0

Lifted waitAnyCatchCancel.

Since: 0.1.0.0

Lifted waitEither.

Since: 0.1.0.0

Lifted waitEitherCatch.

Since: 0.1.0.0

Lifted waitEitherCancel.

Since: 0.1.0.0

Lifted waitEitherCatchCancel.

Since: 0.1.0.0

Lifted waitEither_.

Since: 0.1.0.0

Lifted waitBoth.

Since: 0.1.0.0

Lifted link.

Since: 0.1.0.0

Lifted link2.

Since: 0.1.0.0

Unlifted race.

Since: 0.1.0.0

Unlifted race_.

Since: 0.1.0.0

Unlifted concurrently.

Since: 0.1.0.0

Unlifted concurrently_.

Since: 0.1.0.0

Unlifted Concurrently.

Since: 0.1.0.0

Similar to mapConcurrently but with arguments flipped

Since: 0.1.0.0

Similar to mapConcurrently_ but with arguments flipped

Since: 0.1.0.0

Unlifted replicateConcurrently.

Since: 0.1.0.0

Unlifted replicateConcurrently_.

Since: 0.1.0.0

Executes a Traversable container of items concurrently, it uses the Flat type internally.

Since: 0.1.0.0

Executes a Traversable container of items concurrently, it uses the Flat type internally. This function ignores the results.

Since: 0.1.0.0

A more efficient alternative to Concurrently, which reduces the number of threads that need to be forked. For more information, see FIXME link to blog post. This is provided as a separate type to Concurrently as it has a slightly different API.

Use the conc function to construct values of type Conc, and runConc to execute the composed actions. You can use the Applicative instance to run different actions and wait for all of them to complete, or the Alternative instance to wait for the first thread to complete.

In the event of a runtime exception thrown by any of the children threads, or an asynchronous exception received in the parent thread, all threads will be killed with an AsyncCancelled exception and the original exception rethrown. If multiple exceptions are generated by different threads, there are no guarantees on which exception will end up getting rethrown.

For many common use cases, you may prefer using helper functions in this module like mapConcurrently.

There are some intentional differences in behavior to Concurrently:

• Children threads are always launched in an unmasked state, not the inherited state of the parent thread.

Note that it is a programmer error to use the Alternative instance in such a way that there are no alternatives to an empty, e.g. runConc (empty | empty). In such a case, a ConcException will be thrown. If there was an Alternative in the standard libraries without empty, this library would use it instead.

Since: 0.2.9.0

Construct a value of type Conc from an action. Compose these values using the typeclass instances (most commonly Applicative and Alternative) and then run with runConc.

Since: 0.2.9.0

Run a Conc value on multiple threads.

Since: 0.2.9.0

Flattened structure, either Applicative or Alternative

Flattened Applicative. No Alternative stuff directly in here, but may be in the children. Notice this type doesn't have a type parameter for monadic contexts, it hardwires the base monad to IO given concurrency relies eventually on that.

Since: 0.2.9.0

Things that can go wrong in the structure of a Conc. These are programmer errors.

Since: 0.2.9.0

Simple difference list, for nicer types below

Turn a Conc into a Flat. Note that thanks to the ugliness of empty, this may fail, e.g. flatten Empty.

Since: 0.2.9.0

Run a Flat a on multiple threads.

Like mapConcurrently from async, but instead of one thread per element, it does pooling from a set of threads. This is useful in scenarios where resource consumption is bounded and for use cases where too many concurrent tasks aren't allowed.

Example usage

import Say

action :: Int -> IO Int
action n = do
  tid <- myThreadId
  sayString $ show tid
  threadDelay (2 * 10^6) -- 2 seconds
  return n

main :: IO ()
main = do
  yx <- pooledMapConcurrentlyN 5 (\x -> action x) [1..5]
  print yx

$ ./pool
ThreadId 36
ThreadId 38
ThreadId 40
ThreadId 42
ThreadId 44
[1,2,3,4,5]

import Say

action :: Int -> IO Int
action n = do
  tid <- myThreadId
  sayString $ show tid
  threadDelay (2 * 10^6) -- 2 seconds
  return n

main :: IO ()
main = do
  yx <- pooledMapConcurrentlyN 3 (\x -> action x) [1..5]
  print yx

$ ./pool
ThreadId 35
ThreadId 37
ThreadId 39
ThreadId 35
ThreadId 39
[1,2,3,4,5]

Since: 0.2.10

Similar to pooledMapConcurrentlyN but with number of threads set from getNumCapabilities. Usually this is useful for CPU bound tasks.

Since: 0.2.10

Similar to pooledMapConcurrentlyN but with flipped arguments.

Since: 0.2.10

Similar to pooledForConcurrentlyN but with number of threads set from getNumCapabilities. Usually this is useful for CPU bound tasks.

Since: 0.2.10

Performs the actual pooling for the tasks. This function will continue execution until the task queue becomes empty. When one of the pooled thread finishes it's task, it will pickup the next task from the queue if an job is available.

Like pooledMapConcurrentlyN but with the return value discarded.

Since: 0.2.10

Like pooledMapConcurrently but with the return value discarded.

Since: 0.2.10

Like pooledMapConcurrently_ but with flipped arguments.

Since: 0.2.10

Like pooledMapConcurrentlyN_ but with flipped arguments.

Since: 0.2.10

Pooled version of replicateConcurrently. Performs the action in the pooled threads.

Since: 0.2.10

Similar to pooledReplicateConcurrentlyN but with number of threads set from getNumCapabilities. Usually this is useful for CPU bound tasks.

Since: 0.2.10

Pooled version of replicateConcurrently_. Performs the action in the pooled threads.

Since: 0.2.10

Similar to pooledReplicateConcurrently_ but with number of threads set from getNumCapabilities. Usually this is useful for CPU bound tasks.

Since: 0.2.10