From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 62356@debbugs.gnu.org
Subject: [bug#62356] [PATCH guix-artwork] website: posts: Add Dissecting Guix, Part 3: G-Expressions.
Date: Wed, 12 Apr 2023 17:06:18 +0100 [thread overview]
Message-ID: <87r0sp6ppe.fsf@disroot.org> (raw)
In-Reply-To: <87ile1glv6.fsf@gmail.com>
Hi,
Thanks for the review! :D
Simon Tournier <zimon.toutoune@gmail.com> writes:
>> +The shortcomings of using s-expressions in this way are numerous: we have to
>> +convert everything to a derivation before using it, and _inputs are not an
>> +inherent aspect of the builder_. G-expressions were designed to overcome these
>> +issues.
>
> Here I would link to the paper introducing G-expressions,
>
> https://hal.inria.fr/hal-01580582v1
Good idea. I'll do that :)
> Well, maybe it is a bit stretching and is probably not natural at all
> but I would try to introduce some unquote in sexp-builder. I think it
> would help to see the parallel between S-exp and G-exp; well how G-exp
> extend S-exp as you explained in the introduction.
I'll try, but no guarantees I'll be able to make that make sense.
> From a stylistic point of view, I would write ’S-expressions’ in plain
> and not S-exps or sexps…
>
> …Similarly for G-expression. Both over all the post. Except when it
> refers to code as ’gexp-builder’.
Okay.
> Before the brief digression, I would do another. ;-) Mention ,build and
> ,lower from “guix repl”.
,LOWER is mentioned in part 1
<https://guix.gnu.org/en/blog/2023/dissecting-guix-part-1-derivations/>;
I should have mentioned ,BUILD there too, but it's too late now, and
I don't think such an explanation fits a post meant to explain how gexps
work.
> Hum, maybe #~' needs an explanation. Well, using G-expressions, I am
> missing why Schemers are complaining about Haskell syntax. ;-)
Heh :) (I think it's more to do with Haskell's complexity than ease of
reading.) I'll try to add a short note there.
> Here, I would link to another introduction of G-expression,
>
> https://archive.fosdem.org/2020/schedule/event/gexpressionsguile/
>
> or maybe in the Conclusion section.
Yeah, I'll put the other references in the Conclusion.
> Maybe instead of ’silly’, I would pick another name as ’simple’ or
> ’empty’ or ’trivial’ or ’not-serious’ or else. :-)
>
> And similarly for snippets from above.
Okay.
> Maybe, you could link to Arun’s or Marius’s posts; for the ones I am
> aware of. :-)
>
> https://www.systemreboot.net/post/deploy-scripts-using-g-expressions
> https://gexp.no/blog/guix-drops-part-3-g-expressions.html
Yup, and the FOSDEM talk in the same place.
next prev parent reply other threads:[~2023-04-12 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 20:57 [bug#62356] [PATCH guix-artwork] website: posts: Add Dissecting Guix, Part 3: G-Expressions ( via Guix-patches via
2023-04-12 15:29 ` Simon Tournier
2023-04-12 16:06 ` ( via Guix-patches via [this message]
2023-04-15 22:29 ` [bug#62356] [PAtCH " ( via Guix-patches via
2023-04-18 19:55 ` [bug#62356] [PATCH " Ludovic Courtès
2023-04-18 20:05 ` ( via Guix-patches via
2023-04-18 20:08 ` ( via Guix-patches via
2023-04-19 8:16 ` Simon Tournier
2023-04-19 10:00 ` Ludovic Courtès
2023-04-19 14:17 ` bug#62356: " Ludovic Courtès
2023-04-19 15:15 ` [bug#62356] " ( via Guix-patches via
2023-04-19 13:03 ` [bug#62356] [PAtCH " Théo Maxime Tyburn
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0sp6ppe.fsf@disroot.org \
--to=guix-patches@gnu.org \
--cc=62356@debbugs.gnu.org \
--cc=paren@disroot.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).