From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Andrew Tropin <andrew@trop.in>,
Christopher Baines <mail@cbaines.net>,
guix-devel@gnu.org
Subject: Re: ’inherit’ and list-dependent (was Re: branch master updated: gnu: emacs: Add TREE_SITTER_GRAMMAR_PATH support.)
Date: Wed, 22 Feb 2023 10:17:12 +0100 [thread overview]
Message-ID: <86fsayukiv.fsf@gmail.com> (raw)
In-Reply-To: <87k00ad3xg.fsf@gnu.org>
Hi,
On Tue, 21 Feb 2023 at 23:55, Ludovic Courtès <ludo@gnu.org> wrote:
>> However, we could imagine to use ’package/inherit’ or another variant
>> instead of plain ’inherit’ for creating these inherited packages. Doing
>> so, we could collect some information, e.g., in the field ’properties’,
>> which could be used then by --list-dependent.
>
> In effect that means keeping back the chain of inherited objects, which
> would lead to space leaks.
[...]
> I agree it’d be nice to solve. I can’t think of a good way to do that
> though.
What do you mean by “space leaks”?
Well, we already have ways to create variants collecting information, as
’package-with-python2’ or ’package-with-ocamlX.0Y’, and
’package/inherit’ is somehow another one.
Why would it not be a good way?
Cheers,
simon
next prev parent reply other threads:[~2023-02-22 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167610269975.14308.10330520524841229243@vcs2.savannah.gnu.org>
2023-02-11 11:29 ` branch master updated: gnu: emacs: Add TREE_SITTER_GRAMMAR_PATH support Christopher Baines
2023-02-11 12:35 ` Andrew Tropin
2023-02-11 16:54 ` Andrew Tropin
2023-02-12 0:14 ` Ludovic Courtès
2023-02-12 4:24 ` Andrew Tropin
2023-02-14 12:23 ` ’inherit’ and list-dependent (was Re: branch master updated: gnu: emacs: Add TREE_SITTER_GRAMMAR_PATH support.) Simon Tournier
2023-02-14 19:36 ` Gábor Boskovits
2023-02-21 22:55 ` Ludovic Courtès
2023-02-22 9:17 ` Simon Tournier [this message]
2023-02-25 18:10 ` Ludovic Courtès
2023-02-25 19:27 ` Gábor Boskovits
2023-02-27 9:59 ` Simon Tournier
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=86fsayukiv.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=andrew@trop.in \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mail@cbaines.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.
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).