Broadcast channel type that avoids 0 reader space leaks.

Latest on Hackage:[email protected]:1

See all snapshots broadcast-chan appears in

BSD-3-Clause licensed by Merijn Verstraaten
Maintained by Merijn Verstraaten

Module documentation for 0.1.1

This version can be pinned in stack with:[email protected]:4417ac845d09ef7168bda2cfd9d32af42f4864a356c0a9e31ed0e7957e6b750d,2052

A variation of Control.Concurrent.Chan from base, which allows to the easy creation of broadcast channels without the space-leaks that may arise from using Control.Concurrent.Chan.dupChan. The Control.Concurrent.Chan.Chan type from Control.Concurrent.Chan consists of both a read and write end. This presents a problem when one wants to have a broadcast channel that, at times, has zero listeners. To write to a Control.Concurrent.Chan.Chan there must always be a read end and this read end will hold ALL messages alive until read. The simple solution applied in this module is to separate read and write ends. As a result, any messages written to the write end can be immediately garbage collected if there are no active read ends, avoding space leaks.

Depends on 1 package(full list with versions):