From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: gwl-devel@gnu.org
Subject: Re: variable interpolation in code snippets
Date: Tue, 26 Feb 2019 20:04:51 +0100 [thread overview]
Message-ID: <87pnrez7zg.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ23JVVJ2sZsGq2r-Ph50aHpcfYkq1y3Fw9WDOnLhdc08A@mail.gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
> On Tue, 26 Feb 2019 at 09:12, Ricardo Wurmus <rekado@elephly.net> wrote:
>>
>> I thought about adding support for selectors, but I don’t know if I
>> should. Maybe it would be better to allow for named inputs instead,
>> which would result in process-local bindings.
>
> `data-inputs` is often a list, say the genome (genome.fa) and the
> sequences (R1.fq and R2.fq); then the procedure uses each as e.g.
> my-tool -i genome.fa -1 R1.fq -2 R2.fq
>
> Personnally, I find the Snakemake notation clear:
> input:
> genome = genome.fa
> seqA = R1.fq
> seqB = R2.fq
> shell:
> my-tool -i {input.genome} -1 {input.seqA} -2 {input.seqB}
Yes, I think this is pretty nice. I’ll aim for something like this:
--8<---------------cut here---------------start------------->8---
process: foo
data-inputs
named-list
foo = 1
bar = hello
baz = world
procedure # bash { cat {{data-inputs.foo}} {{data-inputs.bar}} }
--8<---------------cut here---------------end--------------->8---
Haven’t thought much about it, but “named-list” (or whatever the final
name) would introduce a let binding or something.
(BTW: I don’t like that it’s called “data-inputs”. “inputs” is nicer and
fits well to “outputs”.)
--
Ricardo
next prev parent reply other threads:[~2019-02-26 19:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 14:50 variable interpolation in code snippets Ricardo Wurmus
2019-02-25 23:00 ` zimoun
2019-02-26 8:12 ` Ricardo Wurmus
2019-02-26 17:35 ` zimoun
2019-02-26 19:04 ` Ricardo Wurmus [this message]
2019-02-26 19:29 ` zimoun
2019-05-29 13:27 ` Ricardo Wurmus
2019-06-03 14:54 ` zimoun
2019-06-03 16:04 ` Ricardo Wurmus
2019-06-03 18:19 ` Roel Janssen
2019-06-07 14:59 ` 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=87pnrez7zg.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).