From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Autloading seq.el functions
Date: Thu, 24 Oct 2019 13:43:14 +0200 [thread overview]
Message-ID: <87y2xafjxp.fsf@gnus.org> (raw)
In-Reply-To: <jwvpninpirf.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 23 Oct 2019 12:00:58 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> I see we have currently 2 functions autoloaded from seq.el:
> seq-find and seq-position.
>
> While I can live with it, I find it unsatisfactory: these seem
> completely arbitrary since they're not in any obvious sense more "entry
> points" than other functions in that library.
Eli suggested this methodology as a way to use seq.el in pre-dumped
files without pre-dumping seq.el in Emacs (and as a way to determine
whether seq.el is really needed). I suspect that we'll end up (after a
year or two) having all the functions in seq.el ;;;###autoloaded.
> Maybe there are good reasons why these two specifically need to be
> autoloaded while it's not nearly as important for the others, but if so
> I'd like to have some comment explaining it, otherwise it's odd to see
> some package use `seq-*` functions without requiring `seq` while most
> others have to require `seq`.
That's really an intermediary artefact while this is being worked out --
I suspect that in Emacs 29 no packages will have to require seq.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-24 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 16:00 Autloading seq.el functions Stefan Monnier
2019-10-23 18:05 ` Eli Zaretskii
2019-10-24 11:43 ` Lars Ingebrigtsen [this message]
2019-10-26 22:17 ` Juri Linkov
2019-10-27 4:49 ` Eli Zaretskii
2019-10-27 17:26 ` Stefan Monnier
2019-10-27 17:52 ` Eli Zaretskii
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=87y2xafjxp.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.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 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.