This monad transformer adds the ability to fail or throw exceptions to a monad.
A sequence of actions succeeds, producing a value, only if all the actions in the sequence are successful. If one fails with an error, the rest of the sequence is skipped and the composite action fails with that error.
If the value of the error is not required, the variant in Control.Monad.Trans.Maybe may be used instead.
An exception to be thrown.
Minimal complete definition: noMsg or strMsg.
Workaround so that we can have a Haskell 98 instance Error String.
The error monad transformer. It can be used to add error handling to other monads.
The ErrorT Monad structure is parameterized over two things:
* e - The error type.
* m - The inner monad.
The return function yields a successful computation, while >>= sequences two subcomputations, failing on the first error.
This philosophy behind this package is that it is often better to find out all of the errors that have occured in a computation and report them simultaneously, rather than aborting as soon as the first error is encountered. Towards this end, this module supplies a type of combinable error messages so that all of the errors from subcomputations can be gathered and presented together.
New in version 1.1: Removed Monoid instance for Doc (it should now be supplied by ansi-wl-pprint), added ErrorMessageOr type alias.
The one-stop shop for all your error-handling needs! Just import Control.Error.
This library encourages an error-handling style that directly uses the type system, rather than out-of-band exceptions.
Map the unwrapped computation using the given function.
* (mapErrorT f m) = f (runErrorT
A small library useful for error handling when making foreign calls to the Windows API. Error codes set by Windows are converted to Haskell exceptions and can be thrown and caught with the usual exception handling functions in Control.Exception.