unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>,
	stefan@marxist.se, all_but_last@163.com, emacs-devel@gnu.org
Subject: Re: Preloading seq.el
Date: Fri, 06 Sep 2019 09:46:28 +0200	[thread overview]
Message-ID: <m2tv9p7tpn.fsf@gmail.com> (raw)
In-Reply-To: <835zm57v9l.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 06 Sep 2019 10:12:54 +0300")

>>>>> On Fri, 06 Sep 2019 10:12:54 +0300, Eli Zaretskii <eliz@gnu.org> said:

    >> From: Juanma Barranquero <lekktu@gmail.com>
    >> Date: Fri, 6 Sep 2019 02:49:24 +0200
    >> Cc: Zhu Zihao <all_but_last@163.com>, stefan@marxist.se, 
    >> Emacs developers <emacs-devel@gnu.org>
    >> 
    >> A better metrics (but hard to estimate) is how many times a function of cl-lib has been reimplemented (likely in
    >> a much simpler way), or how many workarounds are in place because someone wanted to use a cl-lib
    >> function in the pre-loaded code, but couldn't, and didn't have the energy to try to convince emacs-devel to
    >> preload cl-lib ;-)

    Eli> Only those of the cases where autoloading wouldn't have solved the
    Eli> issue.

    >> I mean, cl-lib is infrastructure code. It's useful and
    >> expressive. If it were preloaded, people would find uses for it.

    Eli> They can use it now by autoloading cl-lib functions they need.

Hmm, if cl-lib is that useful, could we not make people's lives easier
by just slapping autoload cookies on all of it?

Robert



  reply	other threads:[~2019-09-06  7:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 12:21 Preloading seq.el Stefan Kangas
2019-08-29 12:30 ` Lars Ingebrigtsen
2019-08-29 12:47   ` Eli Zaretskii
2019-08-29 12:50     ` Lars Ingebrigtsen
2019-08-29 14:59       ` Eli Zaretskii
2019-08-29 15:15         ` Lars Ingebrigtsen
2019-08-29 15:20           ` Eli Zaretskii
2019-08-29 15:35             ` Lars Ingebrigtsen
2019-08-29 18:41               ` Eli Zaretskii
2019-08-29 18:43                 ` Lars Ingebrigtsen
2019-08-29 21:44                   ` Stefan Monnier
2019-08-29 15:20   ` Stefan Monnier
2019-08-29 12:44 ` Eli Zaretskii
2019-08-31 12:33 ` Zhu Zihao
2019-08-31 12:38   ` Eli Zaretskii
2019-09-06  0:49     ` Juanma Barranquero
2019-09-06  7:12       ` Eli Zaretskii
2019-09-06  7:46         ` Robert Pluim [this message]
2019-09-06  8:23           ` Eli Zaretskii
2019-09-06 11:27         ` Juanma Barranquero

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=m2tv9p7tpn.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=all_but_last@163.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=stefan@marxist.se \
    /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).