explicit-exception

Exceptions which are explicit in the type signature.

http://www.haskell.org/haskellwiki/Exception

Version on this page:	0.1.8
LTS Haskell 23.19:	0.2@rev:2
Stackage Nightly 2025-04-30:	0.2@rev:2
Latest on Hackage:	0.2@rev:2

See all snapshots explicit-exception appears in

BSD-3-Clause licensed and maintained by Henning Thielemann

This version can be pinned in stack with:explicit-exception-0.1.8@sha256:5bd8b23e92c0d5035e2f470479d74fa98ad60811e503536763a0cfde17688ddc,4015

Module documentation for 0.1.8

Control
- Control.Monad
  - Control.Monad.Exception
    - Control.Monad.Exception.Asynchronous
      - Control.Monad.Exception.Asynchronous.Lazy
      - Control.Monad.Exception.Asynchronous.Strict
    - Control.Monad.Exception.Synchronous

Depends on 3 packages(full list with versions):

base, deepseq, transformers

Used by 8 packages in lts-7.24(full list with versions):

audacity, cabal-sort, cutter, equal-files, midi, spreadsheet, tagchup, xml-basic

Synchronous and Asynchronous exceptions which are explicit in the type signature. The first ones are very similar to Either and Control.Monad.Error.ErrorT. The second ones are used for System.IO.readFile and System.IO.hGetContents. This package is a proposal for improved exception handling in Haskell. It strictly separates between handling of exceptional situations (file not found, invalid user input, see http://www.haskell.org/haskellwiki/Exception) and (programming) errors (division by zero, index out of range, see http://www.haskell.org/haskellwiki/Error). Handling of the first one is called "exception handling", whereas handling of errors is better known as "debugging".

For applications see the packages midi, spreadsheet, http-monad.

Although I'm not happy with the identifier style of the Monad Transformer Library (partially intended for unqualified use) I have tried to adopt it for this library, in order to let Haskell programmers get accustomed easily to it.

To do: Because many people requested it, we will provide a bracket function that frees a resource both when an exception and an error occurs, that is, it combines exception handling and debugging. However note that freeing resources in case of an error is dangerous and may cause further damage.