From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Philipp Stephani <p.stephani2@gmail.com>,
Robert Pluim <rpluim@gmail.com>,
Alexander Asteroth <alexander.asteroth@h-brs.de>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: elisp code to list interactive functions
Date: Thu, 04 Nov 2021 16:20:43 -0400 [thread overview]
Message-ID: <jwvpmrfllo7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <871r3vr83e.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 04 Nov 2021 21:15:01 +0100")
Lars Ingebrigtsen [2021-11-04 21:15:01] wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> (seq-filter #'commandp obarray)
>> Sweet: not only the code is shorter, but the returned value is much
>> shorter as well ;-)
> Win win!
> I thought somebody had extended the seq functions to also work on these
> thingies, but I guess not?
Nope. I did provide a patch which introduced a separate type for
obarrays, but it come with some rough corners, and in any case it
introduces a backward incompatibility with fairly limited advantages, so
it's not clear it's a good idea.
But until such a thing is done, we can't reliably distinguish an obarray
from a vector.
This said, an obarray is fundamentally unordered, so it would be odd for
`seq.el` to support it.
Stefan
next prev parent reply other threads:[~2021-11-04 20:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 8:08 elisp code to list interactive functions Alexander Asteroth
2021-11-04 9:43 ` Po Lu
2021-11-04 9:44 ` Robert Pluim
2021-11-04 10:49 ` Alexander Asteroth
2021-11-04 11:51 ` Philipp Stephani
2021-11-04 16:14 ` Alexander Asteroth
2021-11-04 17:07 ` Lars Ingebrigtsen
2021-11-04 17:32 ` Robert Pluim
2021-11-04 17:44 ` Andreas Schwab
2021-11-04 20:06 ` Stefan Monnier
2021-11-04 20:15 ` Lars Ingebrigtsen
2021-11-04 20:20 ` Stefan Monnier [this message]
2021-11-05 2:08 ` Lars Ingebrigtsen
2021-11-05 0:12 ` Po Lu
2021-11-04 19:34 ` Stefan Monnier
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=jwvpmrfllo7.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=alexander.asteroth@h-brs.de \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=p.stephani2@gmail.com \
--cc=rpluim@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).