From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: Preparing for a new release
Date: Mon, 10 Feb 2020 08:43:36 +0100 [thread overview]
Message-ID: <CAJ3okZ0CtaTvaGahZwsHtytf7v_x-ZpByhpAkQEnnTQ4=ie-Kw@mail.gmail.com> (raw)
In-Reply-To: <875zgfosvi.fsf@elephly.net>
On Mon, 10 Feb 2020 at 07:31, Ricardo Wurmus <rekado@elephly.net> wrote:
> zimoun <zimon.toutoune@gmail.com> writes:
> >> * It’s not possible to select more than one tagged item
> >>
> >> In my test workflow I’m generating a bunch of inputs by mapping over
> >> an argument list. Now the problem is that I can’t select all of these
> >> inputs easily in a code snippet. With the syntax we have I can only
> >> select the first item following a tag.
> >>
> >> To address this I’ve extended the accessor syntax, so this works now:
> >>
> >> --8<---------------cut here---------------start------------->8---
> >> process frobnicate
> >> packages "frobnicator"
> >> inputs
> >> . genome: "hg19.fa"
> >> . samples: "a" "b" "c"
> >> outputs
> >> . "result"
> >> # {
> >> frobnicate -g {{inputs:genome}} --files {{inputs::samples}} > {{outputs}}
> >> }
> >> --8<---------------cut here---------------end--------------->8---
> >>
> >> Note how {{inputs::samples}} is substituted with “a b c”. With just a
> >> single colon it would be just “a”. Single colon = single item; double
> >> colon = more than one item.
> >
> > I am confused by the syntax.
> > Well how to select the second element "b"?
> >
> > Naively, I would tempt to write {{inputs:samples:2}} or {{inputs::samples:2}}.
>
> There’s no syntax for that because you can use good ol’ list processing
> (let’s call it “Listp”, or perhaps “Lisp”…) to work on this outside of
> the code snippet.
If I understand correctly, for such cases, 3 solutions:
1. manually split
inputs
. sample-1: "a"
. sample-2: "b"
. sample-3: "c"
or 2. split elsewhere 'samples' using piece of Lisp
or 3. use Lisp features
inputs
. sample-1: `(list-ref ,samples 1)
. sample-2: `(list-ref ,samples 2)
. sample-3: `(list-ref ,samples 3)
Right?
> My hope is that in-list access is much less common and could either be
> rewritten to place the item of interest in the first place, or could be
> solved with a let binding.
It makes sense to me.
All the best,
simon
next prev parent reply other threads:[~2020-02-10 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 12:39 Preparing for a new release Ricardo Wurmus
2020-02-08 20:38 ` Kyle Meyer
2020-02-08 21:50 ` Ricardo Wurmus
2020-02-09 13:00 ` Ricardo Wurmus
2020-02-09 23:33 ` zimoun
2020-02-10 1:25 ` Kyle Meyer
2020-02-10 7:34 ` zimoun
2020-02-10 6:31 ` Ricardo Wurmus
2020-02-10 7:43 ` zimoun [this message]
2020-02-10 21:28 ` Ricardo Wurmus
2020-02-10 23:43 ` zimoun
2020-02-11 9:39 ` Ricardo Wurmus
2020-02-11 9:34 ` Ricardo Wurmus
2020-02-11 15:37 ` zimoun
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='CAJ3okZ0CtaTvaGahZwsHtytf7v_x-ZpByhpAkQEnnTQ4=ie-Kw@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--cc=rekado@elephly.net \
/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).