concurrent-split: MVars and Channels with distinguished input and output side
MVars and Channels with distinguished input and output side. When threads communicate via an MVar or a Chan there are often clearly defined roles, which thread is the sender and which one is receiver. We provide wrappers around the standard concurrency communication channels that make the distinction clear and type safe.
For example, if a function has a parameter of type TChan.In
then it is sure that it will only write to that channel.
Additionally if the compiler warns about an unused TChan.Out
that was created by TChan.new
then you know that the receiver part of your communication is missing.
See also package stm-split
for transactional communication.
This package follows the same idea as chan-split
but is strictly Haskell 98.
Downloads
- concurrent-split-0.0.tar.gz [browse] (Cabal source package)
- Package description (as included in the package)
Maintainer's Corner
For package maintainers and hackage trustees
Candidates
Versions [RSS] | 0.0, 0.0.0.1, 0.0.0.2, 0.0.1, 0.0.1.1 |
---|---|
Dependencies | base (>=4 && <5) [details] |
Tested with | ghc ==6.12.3, ghc ==7.4.1 |
License | BSD-3-Clause |
Author | Henning Thielemann <haskell@henning-thielemann.de> |
Maintainer | Henning Thielemann <haskell@henning-thielemann.de> |
Category | Concurrent |
Source repo | this: darcs get http://code.haskell.org/~thielema/concurrent-split/ --tag 0.0 head: darcs get http://code.haskell.org/~thielema/concurrent-split/ |
Uploaded | by HenningThielemann at 2012-04-10T10:07:25Z |
Distributions | LTSHaskell:0.0.1.1, NixOS:0.0.1.1, Stackage:0.0.1.1 |
Reverse Dependencies | 2 direct, 2 indirect [details] |
Downloads | 4969 total (36 in the last 30 days) |
Rating | (no votes yet) [estimated by Bayesian average] |
Your Rating | |
Status | Docs uploaded by user Build status unknown [no reports yet] |