From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Michael Heerdegen <michael_heerdegen@web.de>
Cc: Eli Zaretskii <eliz@gnu.org>,
"57079@debbugs.gnu.org" <57079@debbugs.gnu.org>,
"stefan@marxist.se" <stefan@marxist.se>,
Juri Linkov <juri@linkov.net>
Subject: bug#57079: 29.0.50; Performance of seq-uniq is not very good
Date: Sat, 20 Aug 2022 15:13:13 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488F4B665C076A12115690CF36F9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87fshrqnkz.fsf@gnus.org>
> We used to limit ourselves to what was in Common Lisp
> when the library was called cl.el, but now that it's cl-lib.el, we've
> opened up the possibility of adding whatever we think is useful in
> Emacs.
Why would/did you do that? Why isn't cl-lib.el
reserved for Common Lisp compatibility code?
An answer of, essentially, "because we've already
made that mistake" isn't, IMHO, a reasonable reason
to continue making it.
"whatever we think is useful in Emacs" - seriously?
Not intending/expecting flames. Just one opinion.
Emacs Lisp could & should have a Common Lisp
compatibility library. That was the original
intention of cl.el, I believe, and that should
still be an intention, regardless of where that
lives. If cl-lib.el is now too far polluted to
serve as that, then maybe consider moving stuff
that does have that intention somewhere else.
prev parent reply other threads:[~2022-08-20 15:13 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
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 [this message]
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=SJ0PR10MB5488F4B665C076A12115690CF36F9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=57079@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
--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).