From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: gwl-devel@gnu.org
Subject: Re: merging “processes” and “restrictions”
Date: Sat, 19 Jan 2019 12:45:33 +0100 [thread overview]
Message-ID: <878szgg9bi.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ1enxGxXxjAVdgNjzU8mwEs8aDquZfLKAaLaT1WLYXUTg@mail.gmail.com>
Hi simon,
> I am not clear yet about how to manage the inputs/outputs
> (fixed in the definition of the process or fixed in the workflow)
[…]
> I am still failing to write a macro that inplements my "view":
> - write the graph
> - collect the inputs/outputs
This is interesting and it might be a solution to this conundrum. If
the processes can declare their inputs without refering to other
processes then we have a solution: the graph can be built from the
inputs and outputs of the provided processes without having to specify
any dependencies manually.
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.
> I pick the name `dataflow' for this not-yet-immplemented macro name.
>
> Well, instead of your graph name, I propose dataflow or stream or datastream.
I’d like this to be a short name if possible. In fact, I’d prefer if it
was completely invisible like this:
(workflow
(name "simple")
(processes
((eat "fruit") -> greet)
((eat "veges") -> greet)
(sleep -> (eat "fruit") (eat "veges"))
(bye -> sleep)))
Or like this assuming that all of the processes declare inputs and
outputs *somehow*:
(workflow
(name "simple")
(processes
(eat "fruit") (eat "veges") greet sleep bye))
I’ll play around with this today.
--
Ricardo
next prev parent reply other threads:[~2019-01-19 11:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 8:55 merging “processes” and “restrictions” Ricardo Wurmus
2019-01-19 10:26 ` zimoun
2019-01-19 11:45 ` Ricardo Wurmus [this message]
2019-01-19 17:55 ` zimoun
2019-01-19 20:51 ` Ricardo Wurmus
2019-01-21 18:45 ` zimoun
2019-01-21 22:51 ` Ricardo Wurmus
2019-01-22 8:49 ` zimoun
2019-01-21 14:43 ` Ricardo Wurmus
2019-01-21 18:53 ` zimoun
2019-01-21 15:32 ` Ricardo Wurmus
2019-01-21 18:55 ` zimoun
2019-01-21 19:33 ` Ricardo Wurmus
2019-01-21 19:59 ` zimoun
2019-01-26 21:49 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878szgg9bi.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gwl-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).