From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
57079@debbugs.gnu.org, stefan@marxist.se,
Juri Linkov <juri@linkov.net>
Subject: bug#57079: 29.0.50; Performance of seq-uniq is not very good
Date: Sat, 13 Aug 2022 22:24:38 +0200 [thread overview]
Message-ID: <87wnbboprt.fsf@web.de> (raw)
In-Reply-To: <87pmh4jraj.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 13 Aug 2022 13:50:44 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I think we're into cl-lib.el territory then -- seq doesn't do KEY.
It would make lots of uses much faster, call it as you like, don't think
about how it's used in CL, it makes sense to add it as functionality to
this function - that's the important part. We can find a different
interface if you prefer that, e.g. allow the test function to be
(TEST F) or something like that.
I have search for occurrences of `seq-uniq' in all elisp files on my
computer, and nearly all non-standard tests fell into this class.
That's why I think we should provide a way to use `seq-uniq' for such
cases. I had not at all been inspired by CL.
Michael.
next prev parent reply other threads:[~2022-08-13 20:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 16:11 bug#57079: 29.0.50; Performance of seq-uniq is not very good Stefan Kangas
2022-08-09 16:47 ` Eli Zaretskii
2022-08-09 16:57 ` Lars Ingebrigtsen
2022-08-09 17:07 ` Eli Zaretskii
2022-08-09 17:21 ` Lars Ingebrigtsen
2022-08-09 17:45 ` Stefan Kangas
2022-08-09 17:18 ` Eli Zaretskii
2022-08-09 17:23 ` Lars Ingebrigtsen
2022-08-09 17:36 ` Eli Zaretskii
2022-08-09 17:50 ` Eli Zaretskii
2022-08-09 17:52 ` Lars Ingebrigtsen
2022-08-09 17:59 ` Eli Zaretskii
2022-08-09 18:03 ` Lars Ingebrigtsen
2022-08-09 18:16 ` Eli Zaretskii
2022-08-09 19:35 ` Juri Linkov
2022-08-12 13:16 ` Lars Ingebrigtsen
2022-08-12 23:59 ` Michael Heerdegen
2022-08-13 11:50 ` Lars Ingebrigtsen
2022-08-13 20:24 ` Michael Heerdegen [this message]
2022-08-15 6:39 ` Lars Ingebrigtsen
2022-08-15 23:37 ` Michael Heerdegen
2022-08-17 11:01 ` Lars Ingebrigtsen
2022-08-20 3:17 ` Michael Heerdegen
2022-08-20 9:19 ` Lars Ingebrigtsen
2022-08-20 15:13 ` 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
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=87wnbboprt.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=57079@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--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).