unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Ricardo Wurmus <rekado@elephly.net>, gwl-devel@gnu.org
Subject: Re: Comments on process template syntax
Date: Sun, 02 Feb 2020 23:30:30 +0000	[thread overview]
Message-ID: <87mua01sa1.fsf@kyleam.com> (raw)
In-Reply-To: <871rrdthmz.fsf@elephly.net>

Hi Ricardo,

Ricardo Wurmus <rekado@elephly.net> writes:

> Hi,
>
> While looking at the examples at https://www.guixwl.org/beyond-started,
> I found that process templates might be difficult to understand, and
> that they have no pretty syntax.
>
> --8<---------------cut here---------------start------------->8---
> process: (list-file-template filename)
>   name
>     string-append "list-file-"
>                   basename filename
>   packages "gzip"
>   inputs filename
>   outputs
>     string-append filename ".list"
>   run-time
>     complexity
>       space 20 mebibytes
>       time  30 seconds
>   # { gzip --list {{inputs}} > {{outputs}} }
> --8<---------------cut here---------------end--------------->8---
>
> The first line is easy to understand for lispers but it might look weird
> to people who come from other workflow languages or programming
> languages.  [...]

Yeah, I agree that first line could be the source of a good amount of
head scratching, though I can't think of a better alternative.  (Then
again, one of the more superficial reasons I like the idea of GWL is the
ability to write in lisp, so I'm probably lacking vision/motivation.)

> (FWIW, I intend to rename the “process:” macro to just “process” to
> remove confusing syntactic noise, so anything about the first line may
> be changed.)

Hmm, but wouldn't that conflict with the `process' constructor defined
in gwl/processes.scm?

  reply	other threads:[~2020-02-02 23:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-02 10:20 Comments on process template syntax Ricardo Wurmus
2020-02-02 23:30 ` Kyle Meyer [this message]
2020-02-03  8:08   ` Ricardo Wurmus
2020-02-03 14:22     ` Kyle Meyer
2020-02-03 15:23       ` Ricardo Wurmus
2020-02-03 23:16         ` Kyle Meyer
2020-02-04  9:55           ` Ricardo Wurmus
2020-02-05  1:48             ` Kyle Meyer
2020-02-05 15:14               ` zimoun
2020-02-03  8:58 ` Roel Janssen
2020-02-03 12:07   ` Ricardo Wurmus
2020-02-03 12:56     ` Roel Janssen
2020-02-03 14:33       ` Ricardo Wurmus
2020-02-04 10:10         ` Ricardo Wurmus
2020-02-05  2:12           ` Kyle Meyer
2020-02-05 15:21           ` zimoun
2020-02-05 15:29             ` Kyle Meyer
2020-02-05 15:37               ` zimoun
2020-02-05 16:02                 ` Kyle Meyer
2020-02-05 16:23                   ` zimoun
2020-02-05 15:07     ` zimoun
2020-02-05 18:04       ` Ricardo Wurmus
2020-02-05 19:14         ` zimoun
2020-02-05 21:32           ` Ricardo Wurmus
2020-02-06 11:59             ` zimoun
2020-02-05 14:56   ` zimoun
2020-02-08 12:34     ` Ricardo Wurmus
2020-02-05 14:50 ` 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=87mua01sa1.fsf@kyleam.com \
    --to=kyle@kyleam.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).