The pipes-core package
Deprecated in favor of pipes
This library offers an abstraction similar in scope to iteratees/enumerators/enumeratees, but with different characteristics and naming conventions.
Difference with traditional iteratees:
Simpler semantics: There is only one data type (Pipe), two primitives (await and yield), and only one way to compose Pipes (>+>). In fact, (>+>) is just convenient syntax for the composition operator in Category. Most pipes can be implemented just using the Monad instance and composition.
Different naming conventions: Enumeratees are called Pipes, Enumerators are Producers, and Iteratees are Consumers. Producers and 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 Pipe.
"Vertical" concatenation works on every 'Pipe': (>>), concatenates Pipes. Since everything is a Pipe, you can use it to concatenate Producers, Consumers, and even intermediate Pipe stages. Vertical concatenation can be combined with composition to create elaborate combinators, without the need of executing pipes in "passes" or resuming partially executed pipes.
Check out Control.Pipe for a copious introduction (in the spirit of the iterIO library), and Control.Pipe.Combinators for some basic combinators and Pipe examples.
- No changelog available
|Dependencies||base (==4.*), categories, lifted-base, monad-control, mtl, void|
|Copyright||2012 Gabriel Gonzalez, 2012 Paolo Capriotti|
|Author||Gabriel Gonzalez, Paolo Capriotti|
|Source repository||head: git clone https://github.com/pcapriotti/pipes-core|
|Upload date||Sat Mar 10 00:26:20 UTC 2012|
- pipes-core-0.0.1.tar.gz [browse] (Cabal source package)
- Package description (included in the package)
For package maintainers and hackage trustees