From: npostavs@users.sourceforge.net
To: Drew Adams <drew.adams@oracle.com>
Cc: Philipp Stephani <p.stephani2@gmail.com>, 25627@debbugs.gnu.org
Subject: bug#25627: 25.1; `help-make-xrefs' loads `cl-extra.el' now
Date: Tue, 07 Feb 2017 23:57:16 -0500 [thread overview]
Message-ID: <87y3xhmg9f.fsf@users.sourceforge.net> (raw)
In-Reply-To: <6cb3cd2a-e972-4542-b85a-7c3d0f18e097@default> (Drew Adams's message of "Tue, 7 Feb 2017 17:59:53 -0800 (PST)")
Drew Adams <drew.adams@oracle.com> writes:
>> > Why don't more (even most) of the files distributed with
>> > Emacs have this variable set (to non-nil)?
>>
>> Loading functions one by one can be slower than loading them all at
>> once. Some justification would be needed for adding this (e.g., if a
>> file contains many independent functions that would usually be used in
>> isolation).
>
> Yes, I read that. A guess would be that that would be the case
> for many more files than the few that use it now.
>
> Files could also be split, to factor out functions for which
> that is true.
Possibly, but I would guess the benefits of doing this would be rather
tiny. I mean, the best we can hope for is to save a few hundred
kilobytes of RAM, right?
next prev parent reply other threads:[~2017-02-08 4:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 18:44 bug#25627: 25.1; `help-make-xrefs' loads `cl-extra.el' now Drew Adams
2017-02-05 19:24 ` Drew Adams
2017-02-07 0:58 ` npostavs
2017-02-07 2:21 ` Drew Adams
2017-02-07 13:30 ` Michael Heerdegen
2017-02-07 16:13 ` Drew Adams
2017-02-07 17:19 ` Michael Heerdegen
2017-02-07 22:29 ` Philipp Stephani
2017-02-07 23:00 ` Drew Adams
2017-02-07 23:08 ` Noam Postavsky
2017-02-08 0:18 ` Drew Adams
2017-02-08 1:56 ` npostavs
2017-02-08 1:59 ` Drew Adams
2017-02-08 4:57 ` npostavs [this message]
2017-02-08 5:40 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3xhmg9f.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=25627@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=p.stephani2@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.