GNU bug report logs - #57079
29.0.50; Performance of seq-uniq is not very good

Previous Next

Package: emacs;

Reported by: Stefan Kangas <stefan <at> marxist.se>

Date: Tue, 9 Aug 2022 16:12:02 UTC

Severity: minor

Found in version 29.0.50

Fixed in version 29.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #79 received at 57079 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>, Michael Heerdegen
 <michael_heerdegen <at> web.de>
Cc: Eli Zaretskii <eliz <at> gnu.org>,
 "57079 <at> debbugs.gnu.org" <57079 <at> debbugs.gnu.org>,
 "stefan <at> marxist.se" <stefan <at> marxist.se>, Juri Linkov <juri <at> linkov.net>
Subject: RE: [External] : bug#57079: 29.0.50; Performance of seq-uniq is not
 very good
Date: Sat, 20 Aug 2022 15:13:13 +0000
> 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.




This bug report was last modified 3 years and 2 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.