From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 67696@debbugs.gnu.org
Subject: bug#67696: 30.0.50; Help deal with multiple versions in load-path
Date: Sun, 17 Dec 2023 18:06:27 -0500 [thread overview]
Message-ID: <jwv8r5se8lv.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CADwFkm=+MrR9ZahQn+FmpfrkGWNht_dDe=e1AZCoUdBsCmN5Xw@mail.gmail.com> (Stefan Kangas's message of "Sun, 17 Dec 2023 09:21:39 -0800")
> Right. On the other hand, perhaps hitting the file system is to some
> extent expected once you start asking for libraries to be loaded. You
> only get the best case `(memq F features)' if that evaluates to `t'.
For top-level uses of `require`, the performance impact is negligible.
But for `require`s used within functions (basically performing manual
autoloads), I'm worried that it could be problematic.
> Personally, I don't have a good view of how common these problems are.
> Perhaps they are relatively uncommon, and it's too much to ask all users
> of `require' to pay a cost for added correctness in unusual cases.
I don't either. That's why I preferred to define a new function, which
lets us gain some experience with it. We may later opt to merge (some
of) its functionality into `require`, of course.
Stefan
next prev parent reply other threads:[~2023-12-17 23:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 16:42 bug#67696: 30.0.50; Help deal with multiple versions in load-path Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-16 19:07 ` Stefan Kangas
2023-12-16 19:50 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-17 17:21 ` Stefan Kangas
2023-12-17 23:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-12-29 14:22 ` Stefan Kangas
2023-12-29 16:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=jwv8r5se8lv.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=67696@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@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 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).