From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: Guix size reduction work group
Date: Tue, 11 Feb 2020 15:15:48 +0100 [thread overview]
Message-ID: <87pnel2orv.fsf@gnu.org> (raw)
In-Reply-To: <878sla1t68.fsf@nckx> (Tobias Geerinckx-Rice's message of "Mon, 10 Feb 2020 14:13:51 +0100")
Hi,
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> Ludovic Courtès 写道:
>> Nope (‘inherit’ is purely syntactic, it doesn’t “live on” at run
>> time.)
>> What would it buy you, though?
>
> In addition to what Gábor mentioned, ‘guix refresh -l’ rebuild numbers
> can be dangerously misleading when inheritance is involved.
>
> Would this not be useful information to record? When I was new here I
> played around with doing just that but my Guile-foo was too weak.
For this specific use case, I agree it would be useful info.
For the more general record use case, I’m skeptical because:
1. (foo (inherit (foo (a 1)))) would no longer be equal? to
(foo (a 1)), which makes little sense from a programming viewpoint.
2. The whole inheritance chain would be kept in memory, when in fact
‘inherit’ is nothing more than syntactic sugar to copy a record.
Maybe we could go fancy and augment ‘define-record-type*’ such that one
can ask for “inheritance reification”, but #2 sounds like that could
quickly make it impractical.
Ludo’.
next prev parent reply other threads:[~2020-02-11 14:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:57 Guix size reduction work group Pierre Neidhardt
2020-02-04 16:22 ` zimoun
2020-02-04 17:59 ` Julien Lepiller
2020-02-05 15:18 ` Ludovic Courtès
2020-02-05 16:11 ` zimoun
2020-02-07 21:35 ` Ludovic Courtès
2020-02-07 22:31 ` Gábor Boskovits
2020-02-08 13:40 ` zimoun
2020-02-10 13:13 ` Tobias Geerinckx-Rice
2020-02-11 14:15 ` Ludovic Courtès [this message]
2020-02-08 16:43 ` Pierre Neidhardt
2020-02-09 23:45 ` zimoun
2020-02-10 8:09 ` Pierre Neidhardt
2020-02-10 8:46 ` Christopher Baines
2020-02-11 14:17 ` Ludovic Courtès
2020-02-10 10:30 ` zimoun
2020-02-10 12:33 ` Julien Lepiller
2020-02-11 14:20 ` Ludovic Courtès
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=87pnel2orv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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).