An effect for atomically reading and modifying a piece of state.

Convention: the interpreter for the AtomicState action must force the resulting tuple of the function, but not the end state or returned value.

Atomically read and modify the state.

The resulting tuple of the computation is forced. You can control what parts of the computation are evaluated by tying their evaluation to the tuple.

Atomically read and strictly modify the state.

The resulting state -- but not the value returned -- is forced.

Read the state.

Depending on the interperation of AtomicState, this can be more efficient than atomicState (\s -> (s,s))

Atomically modify the state.

The resulting state is not forced. atomicModify' is a strict version that does force it.

Atomically and strictly modify the state.

This is a strict version of atomicModify.

Atomically overwrite the state.

You typically don't want to use this, as atomicGet >>= atomicPut . f isn't atomic.

Run an AtomicState effect in terms of atomic operations in IO.

Internally, this simply creates a new IORef, passes it to runAtomicStateIORef, and then returns the result and the final value of the IORef.

This has a higher-rank type, as it makes use of InterpretReifiedC. This makes atomicStateToIO very difficult to use partially applied. In particular, it can't be composed using ..

If performance is secondary, consider using the slower atomicStateToIOSimple, which doesn't have a higher-rank type.

Run an AtomicState effect by transforming it into atomic operations over an IORef.

This has a higher-rank type, as it makes use of InterpretReifiedC. This makes runAtomicStateIORef very difficult to use partially applied. In particular, it can't be composed using ..

If performance is secondary, consider using the slower runAtomicStateIORefSimple, which doesn't have a higher-rank type.

Run an AtomicState effect by transforming it into atomic operations over an TVar.

This has a higher-rank type, as it makes use of InterpretReifiedC. This makes runAtomicStateTVar very difficult to use partially applied. In particular, it can't be composed using ..

If performance is secondary, consider using the slower runAtomicStateTVarSimple, which doesn't have a higher-rank type.

Transform an AtomicState effect into a State effect, discarding atomicity.

Run an AtomicState effect in terms of atomic operations in IO.

Internally, this simply creates a new IORef, passes it to runAtomicStateIORefSimple, and then returns the result and the final value of the IORef.

This is a less performant version of runAtomicStateIORefSimple that doesn't have a higher-rank type, making it much easier to use partially applied.

Run an AtomicState effect by transforming it into atomic operations over an IORef.

This is a less performant version of runAtomicStateIORef that doesn't have a higher-rank type, making it much easier to use partially applied.

Run an AtomicState effect by transforming it into atomic operations over an TVar.

This is a less performant version of runAtomicStateIORef that doesn't have a higher-rank type, making it much easier to use partially applied.