Represents a process identifier.

Specifies a discontinuous process that can suspend at any time and then resume later.

A type class to lift the Process computation to other computations.

Run immediately the process. A new ProcessId identifier will be assigned to the process.

To run the process at the specified time, you can use the enqueueProcess function.

Run immediately the process with the specified identifier. It will be more efficient than as you would specify the process identifier with help of the processUsingId combinator and then would call runProcess.

To run the process at the specified time, you can use the enqueueProcessUsingId function.

Run the process in the start time immediately involving all pending CurrentEvents in the computation too.

Run the process in the start time immediately using the specified identifier and involving all pending CurrentEvents in the computation too.

Run the process in the final simulation time immediately involving all pending CurrentEvents in the computation too.

Run the process in the final simulation time immediately using the specified identifier and involving all pending CurrentEvents in the computation too.

Spawn the child process. In case of cancelling one of the processes, other process will be cancelled too.

Spawn the child process with the specified process identifier. In case of cancelling one of the processes, other process will be cancelled too.

Spawn the child process specifying how the child and parent processes should be cancelled in case of need.

Spawn the child process specifying how the child and parent processes should be cancelled in case of need.

Enqueue the process that will be then started at the specified time from the event queue.

Enqueue the process that will be then started at the specified time from the event queue.

Create a new process identifier.

Return the current process identifier.

Allow calling the process with the specified identifier. It creates a nested process when canceling any of two, or raising an IO exception in any of the both, affects the Process computation.

At the same time, the interruption has no such effect as it requires explicit specifying the ProcessId identifier of the nested process itself, that is the nested process cannot be interrupted using only the parent process identifier.

Hold the process for the specified time period.

Interrupt a process with the specified identifier if the process is held by computation holdProcess.

Test whether the process with the specified identifier was interrupted.

Return the expected interruption time after finishing the holdProcess computation, which value may change if the corresponding process is preempted.

Passivate the process.

Passivate the process before performing some action.

Test whether the process with the specified identifier is passivated.

Reactivate a process with the specified identifier.

Reactivate a process with the specified identifier immediately.

Cancel a process with the specified identifier, interrupting it if needed.

The process cancels itself.

Test whether the process with the specified identifier was cancelled.

Return a signal that notifies about cancelling the process with the specified identifier.

Register a handler that will be invoked in case of cancelling the current process.

Await the signal.

Return a signal when the process is preempted.

Return a signal when the process is proceeded after it was preempted earlier.

Yield to allow other Process and Event computations to run at the current simulation time point.

Try to run the child process within the specified timeout. If the process will finish successfully within this time interval then the result wrapped in Just will be returned; otherwise, the child process will be cancelled and Nothing will be returned.

If an exception is raised in the child process then it is propagated to the parent computation as well.

A cancellation of the child process doesn't lead to cancelling the parent process. Then Nothing is returned within the computation.

Try to run the child process with the given identifier within the specified timeout. If the process will finish successfully within this time interval then the result wrapped in Just will be returned; otherwise, the child process will be cancelled and Nothing will be returned.

If an exception is raised in the child process then it is propagated to the parent computation as well.

A cancellation of the child process doesn't lead to cancelling the parent process. Then Nothing is returned within the computation.

Execute the specified computations in parallel within the current computation and return their results. The cancellation of any of the nested computations affects the current computation. The exception raised in any of the nested computations is propagated to the current computation as well.

Here word parallel literally means that the computations are actually executed on a single operating system thread but they are processed simultaneously by the event queue.

New ProcessId identifiers will be assigned to the started processes.

Like processParallel but allows specifying the process identifiers. It will be more efficient than as you would specify the process identifiers with help of the processUsingId combinator and then would call processParallel.

Like processParallel but ignores the result.

Like processParallelUsingIds but ignores the result.

Exception handling within Process computations.

A computation with finalization part.

Throw the exception with the further exception handling.

By some reason, an exception raised with help of the standard throw function is not handled properly within Process computation, altough it will be still handled if it will be wrapped in the IO monad. Therefore, you should use specialised functions like the stated one that use the throw function but within the IO computation, which allows already handling the exception.

Zip two parallel processes waiting for the both.

Zip three parallel processes waiting for their results.

Unzip the process using memoization so that the both returned processes could be applied independently, although they will refer to the same pair of values.

Memoize the process so that it would always return the same value within the simulation run.

A computation that never computes the result. It behaves like a black hole for the discontinuous process, although such a process can still be canceled outside (see cancelProcessWithId), but then only its finalization parts (see finallyProcess) will be called, usually, to release the resources acquired before.

Retry the current computation as possible, using the specified argument as a SimulationRetry exception message in case of failure.

Like the GoTo statement it transfers the direction of computation, but raises an exception when used within catchProcess or finallyProcess.

Show the debug message with the current simulation time.