assert-failure: Syntactic sugar improving 'assert' and 'error'
This is a package candidate release! Here you can preview how this package release will appear once published to the main package index (which can be accomplished via the 'maintain' link below). Please note that once a package has been published to the main package index it cannot be undone! Please consult the package uploading documentation for more information.
This library contains syntactic sugar that makes it easier
to write simple contracts with assert and error
and report the values that violate contracts.
[Skip to Readme]
Properties
| Versions | 0.1, 0.1.1.0, 0.1.2.0, 0.1.2.0, 0.1.2.1, 0.1.2.2, 0.1.2.3, 0.1.2.4, 0.1.2.5 |
|---|---|
| Change log | None available |
| Dependencies | base (>=4 && <5), pretty-show (>=1.6 && <2), text (>=0.11.2.3 && <2) [details] |
| License | BSD-3-Clause |
| Author | Mikolaj Konarski |
| Maintainer | Mikolaj Konarski <mikolaj.konarski@funktory.com> |
| Category | Control, Contract |
| Home page | https://github.com/Mikolaj/assert-failure |
| Bug tracker | https://github.com/Mikolaj/assert-failure/issues |
| Source repo | head: git clone git://github.com/Mikolaj/assert-failure.git |
| Uploaded | by MikolajKonarski at 2017-09-11T16:45:20Z |
Modules
[Index]
- Control
- Exception
Downloads
- assert-failure-0.1.2.0.tar.gz [browse] (Cabal source package)
- Package description (as included in the package)
Maintainer's Corner
For package maintainers and hackage trustees
Readme for assert-failure-0.1.2.0
[back to package description]assert-failure 
This library contains syntactic sugar that makes it easier to write simple contracts with 'assert' and 'error' and report the values that violate contracts. The original 'assert' function is here re-exported for convenience.
Make sure to enable assertions for your cabal package, e.g., by setting
ghc-options: -fno-ignore-asserts
in your .cabal file. Otherwise, some of the functions will have no effect at all.
The library emerged from the chaos of the tons of assertions (sometimes augmented by comments and trace printouts) and 'error' calls in the LambdaHack game engine.