ivar-simple: Write once concurrency primitives.

[ concurrency, library, mit ] [ Propose Tags ]

IVars are write-once (immutable) variables.

They can be read, an operation that will block until a value was written to the variable. They can be written to exactly once.

[Skip to Readme]
Versions [RSS] [faq],, 0.2, 0.3, 0.3.1, 0.3.2, 0.3.3
Dependencies base (==4.*) [details]
License MIT
Copyright (c) 2008-2012 Bertram Felgenhauer
Maintainer Bertram Felgenhauer <int-e@gmx.de>
Category Concurrency
Uploaded by BertramFelgenhauer at 2012-07-24T10:23:28Z
Distributions NixOS:0.3.3
Downloads 4105 total (33 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs uploaded by user
Build status unknown [no reports yet]




Maintainer's Corner

For package maintainers and hackage trustees


Readme for ivar-simple-0.3

[back to package description]
What is this?

ivar-simple provides immutable, write-once variables (IVars) in the
Data.IVar.Simple module.

It also provides two more experimental channel implementations built on
top of IVars,

        multi-cast channels with write-once semantics.

        channels with write semantics similar to Control.Concurrent.Chan

Comparison to data-ivar

Both data-ivar and ivar-simple provide a write-once variable. That's where
the similarities end:

- Reading an IVar with data-ivar is an IO operation. In ivar-simple it's a
  pure function.
- data-ivar provides a 'Reader' monoid, monad, etc. for reading from one of
  several IVars. ivar-simple has no such functionality.
- The data-ivar implementation can, in principle, add arbitrary IO actions
  that are called when an IVar is written. (This detail is not exposed,
- Technically, ivar-simple tries for efficiency by exploiting the existing
  locking structures in the RTS; in particular, reading a full IVar for a
  second time is as cheap as evaluating a record selector.
  I have no performance numbers for this.