Type of fiber. A fiber represent a suspended computation. Note that using the same fiber twice will execute it twice, which is probably not what you want. To share the result of a fiber, use an Ivar.t.

Create a fiber that has already terminated.

Converts a thunk to a fiber, making sure the thunk runs in the context of the fiber (rather than applied in the current context).

Equivalent to (>>=) (return ()), but more explicit.

Fiber that never completes.

Start two fibers and wait for their results.

Same but assume the first fiber returns unit.

Map a list in parallel.

Iter over a list in parallel.

Variables local to a fiber

with_error_handler f ~on_error calls on_error for every exception raised during the execution of f. This include exceptions raised when calling f () or during the execution of fibers after f () has returned. Exceptions raised by on_error are passed on to the parent error handler.

It is guaranteed that after the fiber has returned a value, on_error will never be called.

fold_errors f ~init ~on_error calls on_error for every exception raised during the execution of f. This include exceptions raised when calling f () or during the execution of fibers after f () has returned.

Exceptions raised by on_error are passed on to the parent error handler.

collect_errors f is: fold_errors f ~init:[] ~on_error:(fun e l -> e :: l)

finalize f ~finally runs finally after f () has terminated, whether it fails or succeeds.

Write once variables

Mailbox variables

Limit the number of jobs

run t ~iter runs a fiber until it terminates. iter is used to implement the scheduler, it should block waiting for an event and return an ivar to fill.