From: "Mattias Engdegård" <mattiase@acm.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 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: Sun, 26 Sep 2021 10:51:12 +0200 [thread overview]
Message-ID: <1060904C-43A4-4981-9E29-5859AD9AB4A5@acm.org> (raw)
In-Reply-To: <508ef22b-02e2-c67b-3e34-be47d22f3328@yandex.ru>
26 sep. 2021 kl. 03.15 skrev Dmitry Gutov <dgutov@yandex.ru>:
> (void-function make-closure)
>
> was a much bigger problem. This is apparently how lambdas are compiled now.
There are no circumstances under which Emacs 28 bytecode is guaranteed to work in earlier Emacs versions: there is backward but no forward compatibility. For example, any code using `with-temp-buffer` won't work, nor as you noticed anything creating closures.
This is unavoidable and the alternative would be much worse, but it's sometimes annoying when testing code with different versions and (in particular) installing packages using a new version and then using an old one.
Could we arrange the .el file to be used if the .elc is built with a newer Emacs version? (Perversely, it would make some inlined functions faster...)
An alternative would be to segregate installed packages by (major) version, so that ~/.emacs.d/ has separate installations for Emacs 26, 27, 28 and so on.
next prev parent reply other threads:[~2021-09-26 8:51 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 [this message]
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
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=1060904C-43A4-4981-9E29-5859AD9AB4A5@acm.org \
--to=mattiase@acm.org \
--cc=50777@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=mardani29@yahoo.es \
--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).