The mtl style typeclass

class Monad m => MonadThrow (m :: Type -> Type) where Source

A class for monads in which exceptions may be thrown.

Instances should obey the following law:

throwM e >> x = throwM e

In other words, throwing an exception short-circuits the rest of the monadic computation.

throwM e >> f = throwM e

class MonadThrow m => MonadCatch (m :: Type -> Type) where Source

A class for monads which allow exceptions to be caught, in particular exceptions which were thrown by throwM.

Instances should obey the following law:

catch (throwM e) f = f e

Note that the ability to catch an exception does not guarantee that we can deal with all possible exit points from a computation. Some monads, such as continuation-based stacks, allow for more than just a success/failure strategy, and therefore catch cannot be used by those monads to properly implement a function such as finally. For more information, see MonadMask.

class MonadCatch m => MonadMask (m :: Type -> Type) where Source

A class for monads which provide for the ability to account for all possible exit points from a computation, and to mask asynchronous exceptions. Continuation-based monads are invalid instances of this class.

Instances should ensure that, in the following code:

fg = f `finally` g

The action g is called regardless of what occurs within f, including async exceptions. Some monads allow f to abort the computation via other effects than throwing an exception. For simplicity, we will consider aborting and throwing an exception to be two forms of "throwing an error".

If f and g both throw an error, the error thrown by fg depends on which errors we're talking about. In a monad transformer stack, the deeper layers override the effects of the inner layers; for example, ExceptT e1 (Except e2) a represents a value of type Either e2 (Either e1 a), so throwing both an e1 and an e2 will result in Left e2. If f and g both throw an error from the same layer, instances should ensure that the error from g wins.

Effects other than throwing an error are also overridden by the deeper layers. For example, StateT s Maybe a represents a value of type s -> Maybe (a, s), so if an error thrown from f causes this function to return Nothing, any changes to the state which f also performed will be erased. As a result, g will see the state as it was before f. Once g completes, f's error will be rethrown, so g' state changes will be erased as well. This is the normal interaction between effects in a monad transformer stack.

By contrast, lifted-base's version of finally always discards all of g's non-IO effects, and g never sees any of f's non-IO effects, regardless of the layer ordering and regardless of whether f throws an error. This is not the result of interacting effects, but a consequence of MonadBaseControl's approach.

generalBracket acquire release use = StateT $ \s0 -> do
  ((b, _s2), (c, s3)) <- generalBracket
    (runStateT acquire s0)
    (\(resource, s1) exitCase -> case exitCase of
      ExitCaseSuccess (b, s2) -> runStateT (release resource (ExitCaseSuccess b)) s2

      -- In the two other cases, the base monad overrides `use`'s state
      -- changes and the state reverts to `s1`.
      ExitCaseException e     -> runStateT (release resource (ExitCaseException e)) s1
      ExitCaseAbort           -> runStateT (release resource ExitCaseAbort) s1
    )
    (\(resource, s1) -> runStateT (use resource) s1)
  return ((b, c), s3)

generalBracket acquire release use = ExceptT $ do
  (eb, ec) <- generalBracket
    (runExceptT acquire)
    (\eresource exitCase -> case eresource of
      Left e -> return (Left e) -- nothing to release, `acquire` didn't succeed
      Right resource -> case exitCase of
        ExitCaseSuccess (Right b) -> runExceptT (release resource (ExitCaseSuccess b))
        ExitCaseException e       -> runExceptT (release resource (ExitCaseException e))
        _                         -> runExceptT (release resource ExitCaseAbort))
    (either (return . Left) (runExceptT . use))
  return $ do
    -- The order in which we perform those two `Either` effects determines
    -- which error will win if they are both `Left`s. We want the error from
    -- `release` to win.
    c <- ec
    b <- eb
    return (b, c)

data ExitCase a Source

A MonadMask computation may either succeed with a value, abort with an exception, or abort for some other reason. For example, in ExceptT e IO you can use throwM to abort with an exception (ExitCaseException) or throwE to abort with a value of type e (ExitCaseAbort).

These functions follow those from Control.Exception, except that they are based on methods from the MonadCatch typeclass. See Control.Exception for API usage.

mask_ :: (HasCallStack, MonadMask m) => m a -> m a Source

Like mask, but does not pass a restore action to the argument.

uninterruptibleMask_ :: (HasCallStack, MonadMask m) => m a -> m a Source

Like uninterruptibleMask, but does not pass a restore action to the argument.

catchAll :: (HasCallStack, MonadCatch m) => m a -> (SomeException -> m a) -> m a Source

Catches all exceptions, and somewhat defeats the purpose of the extensible exception system. Use sparingly.

NOTE This catches all exceptions, but if the monad supports other ways of aborting the computation, those other kinds of errors will not be caught.

catchIOError :: (HasCallStack, MonadCatch m) => m a -> (IOError -> m a) -> m a Source

Catch all IOError (eqv. IOException) exceptions. Still somewhat too general, but better than using catchAll. See catchIf for an easy way of catching specific IOErrors based on the predicates in System.IO.Error.

catchJust :: (HasCallStack, MonadCatch m, Exception e) => (e -> Maybe b) -> m a -> (b -> m a) -> m a Source

A more generalized way of determining which exceptions to catch at run time.

catchIf :: (HasCallStack, MonadCatch m, Exception e) => (e -> Bool) -> m a -> (e -> m a) -> m a Source

Catch exceptions only if they pass some predicate. Often useful with the predicates for testing IOError values in System.IO.Error.

data Handler (m :: Type -> Type) a Source

Generalized version of Handler

catches :: (HasCallStack, Foldable f, MonadCatch m) => m a -> f (Handler m a) -> m a Source

Catches different sorts of exceptions. See Control.Exception's catches

handle :: (HasCallStack, MonadCatch m, Exception e) => (e -> m a) -> m a -> m a Source

Flipped catch. See Control.Exception's handle.

handleAll :: (HasCallStack, MonadCatch m) => (SomeException -> m a) -> m a -> m a Source

Flipped catchAll

handleIOError :: (HasCallStack, MonadCatch m) => (IOError -> m a) -> m a -> m a Source

Flipped catchIOError

handleJust :: (HasCallStack, MonadCatch m, Exception e) => (e -> Maybe b) -> (b -> m a) -> m a -> m a Source

Flipped catchJust. See Control.Exception's handleJust.

handleIf :: (HasCallStack, MonadCatch m, Exception e) => (e -> Bool) -> (e -> m a) -> m a -> m a Source

Flipped catchIf

try :: (HasCallStack, MonadCatch m, Exception e) => m a -> m (Either e a) Source

Similar to catch, but returns an Either result. See Control.Exception's try.

tryJust :: (HasCallStack, MonadCatch m, Exception e) => (e -> Maybe b) -> m a -> m (Either b a) Source

A variant of try that takes an exception predicate to select which exceptions are caught. See Control.Exception's tryJust

onException :: (HasCallStack, MonadCatch m) => m a -> m b -> m a Source

Run an action only if an exception is thrown in the main action. The exception is not caught, simply rethrown.

NOTE The action is only run if an exception is thrown. If the monad supports other ways of aborting the computation, the action won't run if those other kinds of errors are thrown. See onError.

onError :: (HasCallStack, MonadMask m) => m a -> m b -> m a Source

Run an action only if an error is thrown in the main action. Unlike onException, this works with every kind of error, not just exceptions. For example, if f is an ExceptT computation which aborts with a Left, the computation onError f g will execute g, while onException f g will not.

This distinction is only meaningful for monads which have multiple exit points, such as Except and MaybeT. For monads that only have a single exit point, there is no difference between onException and onError, except that onError has a more constrained type.

Since: exceptions-0.10.0

bracket :: (HasCallStack, MonadMask m) => m a -> (a -> m c) -> (a -> m b) -> m b Source

Generalized abstracted pattern of safe resource acquisition and release in the face of errors. The first action "acquires" some value, which is "released" by the second action at the end. The third action "uses" the value and its result is the result of the bracket.

If an error is thrown during the use, the release still happens before the error is rethrown.

Note that this is essentially a type-specialized version of generalBracket. This function has a more common signature (matching the signature from Control.Exception), and is often more convenient to use. By contrast, generalBracket is more expressive, allowing us to implement other functions like bracketOnError.

bracket_ :: (HasCallStack, MonadMask m) => m a -> m c -> m b -> m b Source

Version of bracket without any value being passed to the second and third actions.

finally :: (HasCallStack, MonadMask m) => m a -> m b -> m a Source

Perform an action with a finalizer action that is run, even if an error occurs.

bracketOnError :: (HasCallStack, MonadMask m) => m a -> (a -> m c) -> (a -> m b) -> m b Source

Like bracket, but only performs the final action if an error is thrown by the in-between computation.

class (Typeable e, Show e) => Exception e where

data SomeException