From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Liliana Marie Prikler" <liliana.prikler@gmail.com>
Cc: Andrew Tropin <andrewtropin@gmail.com>,
55653@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#55653] [PATCH] guix: Add syntactic sugar for profile generation.
Date: Thu, 02 Jun 2022 17:07:46 +0200 [thread overview]
Message-ID: <49464e89e7ef5970577319264f1d37d17dc44faf.camel@telenet.be> (raw)
In-Reply-To: <87sfonp4vr.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
Ludovic Courtès schreef op do 02-06-2022 om 15:32 [+0200]:
> Still I’m not a fan of having syntax that looks like a field but is not
> an actual field, if we can avoid it. I prefer to expose the data
> structure as it exists and, if needed, to build abstractions on top of
> it. (The ABI issue that Maxime mention is real but I don’t think it’s a
> big problem in practice.)
FWIW I've some ideas for stable ABIs for record constructors even when
fields are added/removed or change from direct/thunked/delayed, a
stable ABI can be defined later.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-02 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 9:01 [bug#55653] [PATCH] guix: Add syntactic sugar for profile generation Liliana Marie Prikler
2022-05-27 12:39 ` andrew
2022-05-31 13:47 ` Ludovic Courtès
2022-05-31 18:07 ` Liliana Marie Prikler
2022-06-01 19:43 ` Ludovic Courtès
2022-06-01 20:15 ` Liliana Marie Prikler
2022-06-01 20:34 ` Maxime Devos
2022-06-02 13:32 ` Ludovic Courtès
2022-06-02 15:07 ` Maxime Devos [this message]
2022-06-02 16:51 ` Liliana Marie Prikler
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=49464e89e7ef5970577319264f1d37d17dc44faf.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55653@debbugs.gnu.org \
--cc=andrewtropin@gmail.com \
--cc=liliana.prikler@gmail.com \
--cc=ludo@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.