Portability  nonportable (type families) 

Stability  experimental 
Maintainer  ross@soi.city.ac.uk 
Safe Haskell  SafeInferred 
 Computation type:
 Computations which can be interrupted and resumed.
 Binding strategy:
 Binding a function to a monadic value creates a new continuation which uses the function as the continuation of the monadic computation.
 Useful for:
 Complex control structures, error handling, and creating coroutines.
 Zero and plus:
 None.
 Example type:

Cont
r a
The Continuation monad represents computations in continuationpassing style
(CPS).
In continuationpassing style function result is not returned,
but instead is passed to another function,
received as a parameter (continuation).
Computations are built up from sequences
of nested continuations, terminated by a final continuation (often id
)
which produces the final result.
Since continuations are functions which represent the future of a computation,
manipulation of the continuation functions can achieve complex manipulations
of the future of the computation,
such as interrupting a computation in the middle, aborting a portion
of a computation, restarting a computation, and interleaving execution of
computations.
The Continuation monad adapts CPS to the structure of a monad.
Before using the Continuation monad, be sure that you have a firm understanding of continuationpassing style and that continuations represent the best solution to your particular design problem. Many algorithms which require continuations in other languages do not require them in Haskell, due to Haskell's lazy semantics. Abuse of the Continuation monad can produce code that is impossible to understand and maintain.
Documentation
class Monad m => MonadCont m whereSource
callCC :: ((a > m b) > m a) > m aSource
callCC
(callwithcurrentcontinuation)
calls a function with the current continuation as its argument.
Provides an escape continuation mechanism for use with Continuation monads.
Escape continuations allow to abort the current computation and return
a value immediately.
They achieve a similar effect to throwError
and catchError
within an Error
monad.
Advantage of this function over calling return
is that it makes
the continuation explicit,
allowing more flexibility and better control
(see examples in Control.Monad.Cont).
The standard idiom used with callCC
is to provide a lambdaexpression
to name the continuation. Then calling the named continuation anywhere
within its scope will escape from the computation,
even if it is many layers deep within nested computations.
MonadCont m => MonadCont (MaybeT m)  
MonadCont m => MonadCont (ListT m)  
MonadCont m => MonadCont (IdentityT m)  
(Monoid w, MonadCont m) => MonadCont (WriterT w m)  
(Monoid w, MonadCont m) => MonadCont (WriterT w m)  
MonadCont m => MonadCont (StateT s m)  
MonadCont m => MonadCont (StateT s m)  
MonadCont m => MonadCont (ReaderT r m)  
(Error e, MonadCont m) => MonadCont (ErrorT e m)  
MonadCont (ContT r m)  
(Monoid w, MonadCont m) => MonadCont (RWST r w s m)  
(Monoid w, MonadCont m) => MonadCont (RWST r w s m) 