Re: merging “processes” and “restrictions”

[Ricardo Wurmus <rekado@elephly.net>]

Ricardo Wurmus <rekado@elephly.net> writes:

> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> We need a procedure that takes any number of processes as inputs and
>> matches inputs with outputs to generate an adjacency list of processes.
>> This shouldn’t be difficult.
>
> This procedure is called “connect” and it is now available.  With
> connect and well-specified inputs and outputs one can now do this:
>
>     (workflow
>      (name "pipeline")
>      (processes
>       (connect compress-files create-files move-archives)))
>
> All of these processes declare inputs and outputs and the correct
> adjacency list is produced by “connect” by matching them up.

Eh, I just noticed that “connect” is a Guile core binding.  To avoid
shadowing a potentially useful feature we better find a new short name
for “connect”.

How about “link”?

--
Ricardo