teardown: Build composable components for your application with clear teardown semantics
The teardown library allows you to reliably execute cleanup sub-routines for allocated resources when a program is initialized; it:
Ensures that teardown sub-routines are executed exactly once, even on the scenario where cleanup is invoked multiple times
Ensures that if errors occur on the execution of one teardown, the error does not propagate to other sub-routines; effectively keeping them isolated.
Requires every sub-routine to be documented at creation time; thus helping tracing your application structure.
Allows tracing the teardown of your application, how is structured, how much time it takes to execute, and what component (if any) failed to finalize.
[Skip to Readme]
|Versions [faq]||0.0.0.1, 0.0.0.2, 0.1.0.0, 0.1.0.1, 0.2.0.0, 0.3.0.0, 0.4.0.0, 0.4.1.0, 0.5.0.0, 0.5.0.1|
|Dependencies||ansi-wl-pprint (>=0.6.7.3), base (>=4.8 && <5), rio (>=0.0.0.0), typed-process (>=0.1.0.0), unliftio (>=0.2.4.0) [details]|
|Copyright||© 2017, 2018 Roman Gonzalez|
|Source repo||head: git clone https://github.com/roman/Haskell-teardown|
|Uploaded||by RomanGonzalez at 2018-04-10T01:47:41Z|
|Downloads||4685 total (5 in the last 30 days)|
|Rating||(no votes yet) [estimated by Bayesian average]|
Docs available [build log]
Last success reported on 2018-04-13 [all 1 reports]
For package maintainers and hackage trustees