Run a "non transient" computation within the underlying state monad, so it is guaranteed that the computation neither can stop neither can trigger additional events/threads

Run the transient computation with a blank state

Run the transient computation with an state

Get the continuation context: closure, continuation, state, child threads etc

Run the closure and the continuation using the state data of the calling thread

Run the closure and the continuation using his own state data

Warning: radiactive untyped stuff. handle with care

Compose a list of continuations

Run the closure (the x in 'x >>= f') of the current bind operation.

Run the continuation (the f in 'x >>= f') of the current bind operation with the current state

run a chain of continuations. It is up to the programmer to assure by construction that each continuation type-check with the next, that the parameter type match the input of the first continuation. Normally this makes sense if it stop the current flow with stop after the invocation

Dynamic serializable data for logging

A sinonym of empty that can be used in a monadic expression. it stop the computation and execute the next alternative computation (composed with <|>)

When the first operand is an asynchronous operation, the second operand is executed once (one single time) when the first completes his first asyncronous operation.

This is useful for spawning asynchronous or distributed tasks that are singletons and that should start when the first one is set up.

for example a streaming where the event receivers are acivated before the senders.

Set the current closure and continuation for the current statement

Reset the closure and continuation. remove inner binds than the previous computations may have stacked in the list of continuations. resetEventCont :: Maybe a -> EventF -> StateIO (TransIO b -> TransIO b)

Set the maximun number of threads for a procedure. It is useful to limit the parallelization of transient code that uses parallel spawn and waitEvents

Delete all the previous child threads generated by the expression taken as parameter and continue execution of the current thread.

Add a label to the current passing threads so it can be printed by debugging calls like showThreads

Return the state of the thread that initiated the transient computation

Return the state variable of the type desired with which a thread, identified by his number in the treee was initiated

Add n threads to the limit of threads. If there is no limit, it set it

Assure that at least there are n threads available

The threads generated in the process passed as parameter will not be killed by `kill*` primitives.

Since there is no thread control, the application run slightly faster.

The threads will be killed when the parent thread dies. That is the default. This can be invoked to revert the effect of freeThreads

kill all the child threads of the current thread

Kill the current thread and the childs

Kill the childs and the thread of an state

Get the state data for the desired type if there is any.

getData specialized for the Transient monad. if Nothing, the monadic computation does not continue.

If there is no such data, getSData silently stop the computation. That may or may not be the desired behaviour. To make sure that this does not get unnoticed, use this construction:

 getSData <|> error "no data"

To have the same semantics and guarantees than get, use a default value:

getInt= getSData <|> return (0 :: Int)

The default value (0 in this case) has the same role than the initial value in a state monad. The difference is that you can define as many get as you need for all your data types.

To distingish two data with the same types, use newtype definitions.

Synonym for getSData

Set session data for this type. retrieved with getData or getSData Note that this is data in a state monad, that means that the update only affect downstream in the monad execution. it is not a global state neither a per user or per thread state it is a monadic state like the one of a state monad.

Modify state data. It accept a function that get the current state (if exist) as parameter. The state will be deleted or changed depending on function result

Synonym for modifyData

Synonym for setData

Generator of identifiers that are unique withing the current monadic sequence They are not unique in the whole program.

Async calls

Variant of parallel that repeatedly executes the IO computation without end

Variant of parallel that execute the IO computation once

in an alternative computation it executes an async operations synchronously. This means that the alternatives do not execute until the async operation finishes. Do not use in Applicatives.

`spawn= freeThreads . waitEvents`

Executes an IO action each certain interval of time and return his value if it changes

Return empty to the current thread and execute the IO action in a new thread. When the IO action returns, the transient computation continues with this value as the result The IO action may be re-executed or not depending on the result. So parallel can spawn any number of threads/results.

If the maximum number of threads, set with threads has been reached parallel perform the work sequentially, in the current thread. So parallel means that 'it can be parallelized if there are thread available'

if there is a limitation of threads, when a thread finish, the counter of threads available is increased so another parallel can make use of it.

The behaviour of parallel depend on StreamData; If SMore, parallel will excute again the IO action. With SLast, SDone and SError, parallel will not repeat the IO action anymore.

kill all the child threads associated with the continuation context

De-invert an event handler.

The first parameter is the setter of the event handler to be deinverted. Usually it is the primitive provided by a framework to set an event handler

the second parameter is the value to return to the event handler. Usually it is `return()`

it configures the event handler by calling the setter of the event handler with the current continuation

Install a event receiver that wait for a string and trigger the continuation when this string arrives.

Validates an input entered in the keyboard in non blocking mode. non blocking means that the user can enter also anything else to activate other option unlike option, wich watch continuously, input only wait for one valid response

Non blocking getLine with a validator

Wait for the execution of exit and return the result or the exhaustion of thread activity

Keep the main thread running, initiate the non blocking keyboard input and execute the transient computation.

It also read a slash-separated list of string that are read by option and input as if they were entered by the keyboard

 foo  -p  options/to/be/read/by/option/and/input

Same than keep but do not initiate the asynchronous keyboard input. Useful for debugging or for creating background tasks, as well as to embed the Transient monad inside another computation. It returns either the value returned by exit. or Nothing, when there is no more threads running

Force the finalization of the main thread and thus, all the Transient block (and the application if there is no more code)

Alternative operator for maybe values. Used in infix mode

Assures that backtracking will not go further back

The second parameter will be executed when backtracking

Register an action that will be executed when backtracking

backtracking is stopped. the exection continues forward from this point on.

Execute backtracking. It execute the registered actions in reverse order.

If the backtracking flag is changed the flow proceed forward from that point on.

If the backtrack stack is finished or undoCut executed, undo will stop.

Initialize the event variable for finalization. all the following computations in different threads will share it it also isolate this event from other branches that may have his own finish variable

Set a computation to be called when the finish event happens

Set a computation to be called when the finish event happens this only apply for

Trigger the event, so this closes all the resources

trigger finish when the stream of data ends

When a exception is produced in the continuation, the handler is executed. | handlers are executed Last in first out.

stop the backtracking mechanism to execute further handlers

Resume to normal execution at this point