From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
50777@debbugs.gnu.org,
"Stefan Monnier" <monnier@iro.umontreal.ca>,
"Daniel Martín" <mardani29@yahoo.es>
Subject: bug#50777: Dropping EIEIO from xref (for performance)
Date: Sat, 25 Sep 2021 04:52:49 +0300 [thread overview]
Message-ID: <938468d9-4fd4-e719-b52c-72199989f177@yandex.ru> (raw)
In-Reply-To: <87lf3lqvkz.fsf@gnus.org>
On 25.09.2021 04:42, Lars Ingebrigtsen wrote:
> Speedups would be nice, but I think this sounds like a very big change
> to make to such a central system (that I think many third-party packages
> rely on) at this point, so I'm leaning towards it being in Emacs 29
> instead.
Xref is an "ELPA core" package. As soon as we make this change on master
and bump the version, it will affect the third-party packages right
away. Not when Emacs 29 is released, year(s) later.
On the flip side, we can make the change now, bump the version, and be
reasonably certain that when Emacs 28 comes out, the third-party
packages are already updated for the version that comes with it.
It's also the most reliable way to work out the kinks that I know of.
next prev parent reply other threads:[~2021-09-25 1:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 13:28 bug#50777: Dropping EIEIO from xref (for performance) Dmitry Gutov
2021-09-24 13:35 ` Dmitry Gutov
2021-09-24 13:37 ` Dmitry Gutov
2021-09-24 14:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-24 15:32 ` Dmitry Gutov
2021-09-26 1:15 ` Dmitry Gutov
2021-09-26 8:51 ` Mattias Engdegård
2021-09-26 18:34 ` Dmitry Gutov
2021-09-24 15:12 ` Arthur Miller
2021-09-25 1:42 ` Lars Ingebrigtsen
2021-09-25 1:52 ` Dmitry Gutov [this message]
2021-09-25 14:07 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-26 2:16 ` Dmitry Gutov
2021-09-30 21:10 ` Dmitry Gutov
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=938468d9-4fd4-e719-b52c-72199989f177@yandex.ru \
--to=dgutov@yandex.ru \
--cc=50777@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mardani29@yahoo.es \
--cc=mattiase@acm.org \
--cc=monnier@iro.umontreal.ca \
/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/emacs.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).