| Copyright | (c) The University of Glasgow 2001 |
|---|---|
| License | BSD-style (see the file libraries/base/LICENSE) |
| Maintainer | libraries@haskell.org |
| Stability | stable |
| Portability | non-portable (requires universal quantification for runST) |
| Safe Haskell | Unsafe |
| Language | Haskell2010 |
GHC.Internal.Control.Monad.ST.Imp
Description
This library provides support for strict state threads, as described in the PLDI '94 paper by John Launchbury and Simon Peyton Jones Lazy Functional State Threads.
The ST Monad
The strict ST monad.
The ST monad allows for destructive updates, but is escapable (unlike IO).
A computation of type returns a value of type ST s aa, and
execute in "thread" s. The s parameter is either
- an uninstantiated type variable (inside invocations of
runST), or RealWorld(inside invocations ofstToIO).
It serves to keep the internal states of different invocations
of runST separate from each other and from invocations of
stToIO.
The >>= and >> operations are strict in the state (though not in
values stored in the state). For example,
runST (writeSTRef _|_ v >>= f) = _|_Instances
| Applicative (ST s) Source # | Since: base-4.4.0.0 |
| Functor (ST s) Source # | Since: base-2.1 |
| Monad (ST s) Source # | Since: base-2.1 |
| MonadFix (ST s) Source # | Since: base-2.1 |
| Monoid a => Monoid (ST s a) Source # | Since: base-4.11.0.0 |
| Semigroup a => Semigroup (ST s a) Source # | Since: base-4.11.0.0 |
| Show (ST s a) Source # | Since: base-2.1 |
runST :: (forall s. ST s a) -> a Source #
Return the value computed by a state thread.
The forall ensures that the internal state used by the ST
computation is inaccessible to the rest of the program.
Converting ST to IO
Unsafe operations
unsafeInterleaveST :: ST s a -> ST s a Source #
unsafeInterleaveST allows an ST computation to be deferred
lazily. When passed a value of type ST a, the ST computation will
only be performed when the value of the a is demanded.
unsafeDupableInterleaveST :: ST s a -> ST s a Source #
unsafeDupableInterleaveST allows an ST computation to be deferred
lazily. When passed a value of type ST a, the ST computation will
only be performed when the value of the a is demanded.
The computation may be performed multiple times by different threads,
possibly at the same time. To prevent this, use unsafeInterleaveST instead.
Since: base-4.11
unsafeIOToST :: IO a -> ST s a Source #
unsafeSTToIO :: ST s a -> IO a Source #
Convert an ST action to an IO action.
This relies on IO and ST having the same representation modulo the
constraint on the state thread type parameter.
For an example demonstrating why this is unsafe, see https://mail.haskell.org/pipermail/haskell-cafe/2009-April/060719.html