concurrent-resource-map: Concurrent resource map
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.
Warnings:
- 'ghc-options: -O2' is rarely needed. Check that it is giving a real benefit and not just imposing longer compile times on your users.
Please see the README on GitHub at https://github.com/Fuuzetsu/concurrent-resource-map#readme
[Skip to Readme]
Properties
| Versions | 0.1.0.0, 0.2.0.0, 0.2.0.0 |
|---|---|
| Change log | ChangeLog.md |
| Dependencies | base [details] |
| License | BSD-3-Clause |
| Copyright | 2020 Mateusz Kowalczyk |
| Author | Mateusz Kowalczyk |
| Maintainer | fuuzetsu@fuuzetsu.co.uk |
| Category | Data |
| Home page | https://github.com/Fuuzetsu/concurrent-resource-map#readme |
| Bug tracker | https://github.com/Fuuzetsu/concurrent-resource-map/issues |
| Source repo | head: git clone https://github.com/Fuuzetsu/concurrent-resource-map |
| Uploaded | by MateuszKowalczyk at 2020-03-18T03:23:23Z |
Modules
[Index] [Quick Jump]
Downloads
- concurrent-resource-map-0.2.0.0.tar.gz [browse] (Cabal source package)
- Package description (as included in the package)
Maintainer's Corner
Package maintainers
For package maintainers and hackage trustees
Readme for concurrent-resource-map-0.2.0.0
[back to package description]concurrent-resource-map 
User-counted resource map with automatic resource collection, aimed to be used in concurrent setting.
Consider having some sort of resource that you need properly initialised and cleaned up but only once and only for as long as there are interested users (threads). Further, instead of only a single resource, you want a collection of such resources, keyed on some value.
This package implements a simple bracket-based scheme that manipulates a resource map by counting number of initalisations and clean-ups: if it detects that the cleanup is from the last user, it removes the resource from the map all together. See the code/hackage for documentation.