| |||||

| |||||

Description | |||||

Provides an instance of Arrow for process pipelines. As described in the original paper on arrows, they can be used to represent stream processing, so CHP seemed like a possible fit for an arrow. Whether this is - If equality means that given the same input value, both arrows produce the same corresponding output value, this is an arrow.
- If equality means you give the arrows the same single input and wait for the single output, and the output is the same, this is an arrow.
- If equality means that you can feed the arrows lots of inputs (one after the other) and the behaviour should be the same with regards to communication, this is not an arrow.
The problem lies in the buffering inherent in arrows. Imagine if I am fairly confident that the arrow laws are satisfied for the definition of equality that given the same single input, they will produce the same single output. If you don't worry too much about the behavioural difference, and just take arrows as another way to wire together a certain class of process network, you should do fine. Added in version 1.0.2. | |||||

Synopsis | |||||

| |||||

Documentation | |||||

| |||||

| |||||

| |||||

Given a The pipeline will run forever (until poisoned) and you must run it in parallel to whatever is feeding it the inputs and reading off the outputs. Imagine that you want a process pipeline that takes in a pair of numbers, doubles the first and adds one to the second. You could encode this in an arrow using: runPipeline (arr (*2) *** arr (+1)) Arrows are more useful where you already have processes written that process data and you want to easily wire them together. The arrow notation is probably easier for doing that than declaring all the channels yourself and composing everything in parallel. | |||||

| |||||

Adds a wrapper that forms this process into the right data type to be part of an arrow. Any process you apply this to should produce exactly one output per
input, or else you will find odd behaviour resulting (including deadlock).
So for example, Added in version 1.1.0 | |||||

Produced by Haddock version 2.3.0 |