The inspection-testing package
Some carefully crafted libraries make promises to their users beyond functionality and performance.
Examples are: Fusion libraries promise intermediate data structures to be eliminated. Generic programming libraries promise that the generic implementation is identical to the hand-written one. Some libraries may promise allocation-free or branch-free code.
Conventionally, the modus operandi in all these cases is that the library author manually inspects the (intermediate or final) code produced by the compiler. This is not only tedious, but makes it very likely that some change, either in the library itself or the surrounding eco-system, breaks the library’s promised without anyone noticing.
This package provides a disciplined way of specifying such properties, and have them checked by the compiler. This way, this checking can be part of the ususal development cycle and regressions caught early.
See the documentation in Test.Inspection or the project webpage for more examples and more information.
[Skip to Readme]
|Versions||0.1, 0.1.1, 0.1.1.1, 0.1.1.2|
|Dependencies||base (>=4.9 && <4.12), containers, ghc (>=8.0.2 && <8.4), template-haskell [details]|
|Copyright||2017 Joachim Breitner|
|Category||Testing, Compiler Plugin|
|Source repository||head: git clone git://github.com/nomeata/inspection-testing.git|
|Uploaded||Sun Nov 12 20:31:22 UTC 2017 by JoachimBreitner|
|Downloads||113 total (113 in the last 30 days)|
|Rating||2.0 (votes: 1) [estimated by rule of succession]|
|Status||Docs available [build log]
Last success reported on 2017-11-12 [all 1 reports]
Hackage Matrix CI
Run tests that pull in specific versions of other packages
Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info
For package maintainers and hackage trustees