Documentation

A Pool manages a collection of possibly interdependent tasks, such that tasks await execution until the tasks they depend on have finished (and tasks may depend on an arbitrary number of other tasks), while independent tasks execute concurrently up to the number of available resource slots in the pool.

Results from each task are available until the status of the task is polled or waited on. Further, the results are kept until that occurs, so failing to ever wait will result in a memory leak.

Tasks may be cancelled, in which case all dependent tasks are unscheduled.

A Handle is a unique reference to a task that has submitted to a Pool.

Create a thread pool for executing interdependent tasks concurrently. The number of available slots governs how many tasks may run at one time.

Begin executing tasks in the given pool. The number of slots determines how many threads may execute concurrently. This number is adjustable dynamically, by calling setPoolSlots, though reducing it does not cause already active threads to stop.

Note: Setting the number of available slots to zero has the effect of causing this function to exit soon after, so that runPool will need to be called again to continue processing tasks in the Pool.

Set the number of available execution slots in the given Pool. Increasing the number will cause waiting threads to start executing immediately, while decreasing the number only decreases any available slots -- it does not cancel already executing threads.

Cancel every running thread in the pool and unschedule any that had not begun yet.

Submit an IO action for execution within the managed thread pool. When it actually begins executes is determined by the number of available slots, whether the threaded runtime is being used, and how long it takes the jobs before it to complete.

Submit a task, but only allow it begin executing once its parent task has completed. This is equivalent to submitting a new task and linking it to its parent using sequenceTasks within a single STM transaction.

Cancel a task submitted to the pool. This will unschedule it if it had not begun yet, or cancel its thread if it had.

Given parent and child task handles, link them so that the child cannot execute until the parent has finished.

Wait until the given task is completed, but re-raise any exceptions that were raised in the task's thread.

Wait until the given task has completed, then return its final status.

Poll the given task, as with pollTaskEither, but re-raise any exceptions that were raised in the task's thread.

Poll the given task, returning Nothing if it hasn't started yet or is currently executing, and a Just value if a final result is known.