concurrent-split: MVars and Channels with distinguished input and output side
|Versions||0.0, 0.0.0.1, 0.0.0.2, 0.0.1|
|Dependencies||base (==4.*) [details]|
|Author||Henning Thielemann <firstname.lastname@example.org>|
|Maintainer||Henning Thielemann <email@example.com>|
|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 Tue Apr 10 10:07:25 UTC 2012|
|Distributions||LTSHaskell:0.0.1, NixOS:0.0.1, Stackage:0.0.1, openSUSE:0.0.1|
|Downloads||1322 total (14 in the last 30 days)|
|Rating||(no votes yet) [estimated by rule of succession]|
|Status||Docs uploaded by user
Build status unknown [no reports yet]
Hackage Matrix CI
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
then it is sure that it will only write to that channel.
Additionally if the compiler warns about an unused
that was created by
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.
For package maintainers and hackage trustees