pipes-core: Compositional pipelines
|Dependencies||base (==4.*), categories (==1.0.*), lifted‑base (==0.1.*), monad‑control (==0.3.*), transformers (>=0.2 && <0.4), void (==0.5.*) [details]|
|Copyright||2012 Gabriel Gonzalez, 2012 Paolo Capriotti|
|Author||Gabriel Gonzalez, Paolo Capriotti|
|Source repo||head: git clone https://github.com/pcapriotti/pipes-core|
|Uploaded||by PaoloCapriotti at Mon Apr 9 21:29:15 UTC 2012|
|Downloads||929 total (9 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
This library offers an abstraction similar in scope to iteratees/enumerators/enumeratees, but with different characteristics and naming conventions.
This package is a fork of the original pipes package by Gabriel Gonzalez. See https://github.com/pcapriotti/pipes-core/wiki/pipes-core-vs-pipes for a comparison between the two packages.
Differences with traditional iteratees:
Simpler semantics: There is only one data type (
Pipe), two basic primitives (
yield), and only one way to compose
>+>). In fact, (
>+>) is just convenient syntax for the composition operator in
Category. Most pipes can be implemented just using the
Monadinstance and composition.
Different naming conventions: Enumeratees are called
Pipes, Enumerators are
Producers, and Iteratees are
Consumers are just type synonyms for
Pipes with either the input or output end closed.
Pipes form a Category: that means that composition is associative, and that there is an identity
Vertical concatenation works on every
Pipes. Since everything is a
Pipe, you can use it to concatenate
Consumers, and even intermediate
Pipestages. Vertical concatenation can be combined with composition to create elaborate combinators, without the need of executing pipes in "passes" or resuming partially executed pipes.
For package maintainers and hackage trustees