assert-failure: Syntactic sugar improving 'assert' and 'error'
This library contains syntactic sugar that improves
the usability of assert and error.
This is actually a bunch of hacks wrapping the original
assert function, see inside.
[Skip to Readme]
Downloads
- assert-failure-0.1.tar.gz [browse] (Cabal source package)
- Package description (as included in the package)
Maintainer's Corner
For package maintainers and hackage trustees
Candidates
- No Candidates
| Versions [RSS] | 0.1, 0.1.1.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, 0.1.2.6, 0.1.3.0 |
|---|---|
| Dependencies | base (>=4 && <5), pretty-show (>=1.6 && <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 2013-12-10T23:21:31Z |
| Distributions | Arch:0.1.3.0, Debian:0.1.2.3, LTSHaskell:0.1.3.0, NixOS:0.1.3.0, Stackage:0.1.3.0 |
| Reverse Dependencies | 2 direct, 1 indirect [details] |
| Downloads | 9994 total (42 in the last 30 days) |
| Rating | 2.0 (votes: 1) [estimated by Bayesian average] |
| Your Rating | |
| Status | Docs available [build log] Successful builds reported [all 1 reports] |
Readme for assert-failure-0.1
[back to package description]assert-failure 
This library contains syntactic sugar that improves the usability of 'assert' and 'error'. This is actually a bunch of hacks wrapping the original 'assert' function, which is, as of GHC 7.8, the only simple way of obtaining source positions. 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 is available from [Hackage] 1 and it's homepage and issue tracker is on [github] 2. The library emerged from the tons of assertions (augmented by comments and printouts) and 'error' calls (marked by unique strings to overcome their lack of source position) in the [LambdaHack] 3 game engine.