From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kyle Meyer Subject: Re: Comments on process template syntax In-Reply-To: <871rrdthmz.fsf@elephly.net> References: <871rrdthmz.fsf@elephly.net> Date: Sun, 02 Feb 2020 23:30:30 +0000 Message-ID: <87mua01sa1.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To: Ricardo Wurmus , gwl-devel@gnu.org List-ID: Hi Ricardo, Ricardo Wurmus 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 =E2=80=9Cprocess:=E2=80=9D macro to just = =E2=80=9Cprocess=E2=80=9D 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?