From: "Štěpán Němec" <stepnem@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 20056@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#20056: 25.0.50; Remove non Common Lisp stuff from cl*.el libraries
Date: Sat, 03 Aug 2019 09:49:27 +0200 [thread overview]
Message-ID: <87o916bse0.fsf@gmail.com> (raw)
In-Reply-To: <871ry3t13k.fsf@gmail.com> (Noam Postavsky's message of "Fri, 02 Aug 2019 22:49:19 -0400")
On Fri, 02 Aug 2019 22:49:19 -0400
Noam Postavsky wrote:
> Things have changed since the original discussion though: now that setf
> has been moved out of cl-lib, I think cl-letf and cl-callf should go
> with it.
As much as I would personally like to get rid of the prefixes, it seems
to me that unless you move _most_ of cl-, you'll only increase the
confusion. Now it's just setf, that's easy to remember, but with more
exceptions one would have to check if a particular form is or isn't
supposed to be used with the prefix all the time (albeit with the help
of the byte compiler).
Considering your proposal in particular, what about shiftf, rotatef?
What makes them different?
--
Štěpán
next prev parent reply other threads:[~2019-08-03 7:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 18:02 bug#20056: 25.0.50; Remove non Common Lisp stuff from cl*.el libraries Drew Adams
2015-03-08 18:12 ` Eli Zaretskii
2015-03-08 19:06 ` Dani Moncayo
2015-03-08 20:10 ` Eli Zaretskii
2016-02-29 20:08 ` Glenn Morris
2016-02-29 20:57 ` Drew Adams
2015-03-08 18:21 ` Daniel Colascione
2015-03-08 18:46 ` Drew Adams
2015-03-08 19:11 ` Daniel Colascione
2015-03-08 21:12 ` Drew Adams
2015-03-08 21:19 ` Daniel Colascione
2015-03-08 21:31 ` Drew Adams
2015-03-09 4:52 ` Stefan Monnier
2019-08-02 12:50 ` Lars Ingebrigtsen
2019-08-03 2:49 ` Noam Postavsky
2019-08-03 7:49 ` Štěpán Němec [this message]
2019-08-03 10:30 ` Lars Ingebrigtsen
2019-08-03 12:58 ` Noam Postavsky
2019-08-03 13:16 ` Štěpán Němec
2019-08-03 21:10 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o916bse0.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=20056@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@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 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.