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: Mon, 03 Jun 2019 18:04:11 +0200 [thread overview]
Message-ID: <87r28airk4.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ1jGnU02to1ZquLXTaOTa=9xHm7k0R-sKiEC_c2DvGPqQ@mail.gmail.com>
Hi simon,
> It improves the readibilty.
> However, does the keyword `list` is mandatory ?
Unfortunately it is mandatory. Previously, I tried to give the record
field a “smart constructor” that takes either one value (a list or a let
binding resulting in a list) or — for convenience – multiple values that
are then turned into a list.
With the Guix-style records this does not seem to be possible. If we
want to make this work we’d have to use our own extended records or
maybe switch to GOOPS. GOOPS offers virtual slots that can have
slot-ref and slot-set! procedures, which would handle the conversion
transparently. I think this would be a good way forward — and it would
decouple the GWL from the Guix version in use, because those extended
record are really made for Guix and may not forever match the needs of
the GWL.
> With the renaming scheme that I proposed:
> - inputs -becomes-> packages
> - data-inputs -becomes-> inputs
> - outputs -becomes-> outputs
I still agree with these changes. We’d only need to find a way to
support the old syntax for a while to allow for migrating existing
workflows (AFAIK that’s really just Roel’s workflows, but it better to
gradually deprecate the previous syntax).
--
Ricardo
next prev parent reply other threads:[~2019-06-03 16: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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r28airk4.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.