From: Michael Heerdegen <michael_heerdegen@web.de>
To: akater <nuclearspace@gmail.com>
Cc: emacs-devel@gnu.org, rms@gnu.org,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Some improvements for cl-flet
Date: Thu, 14 Oct 2021 06:00:15 +0200 [thread overview]
Message-ID: <87mtncjlww.fsf@web.de> (raw)
In-Reply-To: <877demdb5w.fsf@gmail.com> (akater's message of "Sat, 09 Oct 2021 05:23:07 +0000")
akater <nuclearspace@gmail.com> writes:
> > Is there a good reason to support cl-symbol-macrolet at all?
> > It is a bizarre construct.
>
> People largely agree that with-slots is beneficial, for example.
> with-slots wouldn't be possible without symbol-macrolet.
I must say that at first I hated Richard's comments, but now I tend to
agree.
Most of our uses of `symbol-macrolet' are about places. Like
`with-slots'. So you can do (setf var expr).
But does the provided syntax have to look exactly like that? Having
setting a variable change some place as side effect is slightly bizarre
indeed. We could provide the same feature offering a syntax like
(setf (place) expr)
where `place' is a local (normal) macro that "returns" a reference to
the according place. Makes a bit more sense, conceptually. With other
words: we could provide the same using `cl-macrolet' instead of
`symbol-macrolet'.
The only really different example is `thunk-let', a kind of lazy let I
already mentioned. But (docstring): "It is not allowed to set
`thunk-let' or `thunk-let*' bound variables." So there variable
abstraction also doesn't fit so well in that case.
I don't think we should remove `cl-symbol-macrolet', but I have the
impression that all current uses in Emacs could well work without symbol
macros.
Michael.
next prev parent reply other threads:[~2021-10-14 4:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 12:51 Some improvements for cl-flet akater
2021-09-11 23:32 ` Michael Heerdegen
2021-09-12 3:35 ` akater
2021-09-12 15:38 ` Stefan Monnier
2021-09-13 0:14 ` Michael Heerdegen
2021-09-13 2:26 ` Stefan Monnier
2021-10-07 2:32 ` akater
2021-10-07 18:03 ` Stefan Monnier
2021-10-08 21:57 ` Richard Stallman
2021-10-09 5:23 ` akater
2021-10-09 6:01 ` Michael Heerdegen
2021-10-09 23:37 ` Richard Stallman
2021-10-10 10:41 ` Po Lu
2021-10-10 20:27 ` João Távora
2021-10-10 21:57 ` Stefan Monnier
2021-10-11 0:45 ` [External] : " Drew Adams
2021-10-11 21:16 ` Richard Stallman
2021-10-11 21:26 ` João Távora
2021-10-12 22:42 ` Richard Stallman
2021-10-12 0:05 ` Po Lu
2021-10-12 0:29 ` Robin Tarsiger
2021-10-12 22:43 ` Richard Stallman
2021-10-09 23:33 ` Richard Stallman
2021-10-09 23:33 ` Richard Stallman
2021-10-14 4:00 ` Michael Heerdegen [this message]
2021-09-23 22:37 ` [PATCH] " akater
2021-09-23 22:41 ` akater
2021-09-24 7:11 ` João Távora
2021-09-24 15:20 ` [PATCH] Some improvements for cl-flet, and some more akater
2021-09-24 16:22 ` João Távora
2021-09-25 1:28 ` Lars Ingebrigtsen
2021-09-25 8:37 ` João Távora
2021-09-24 20:30 ` [PATCH] Some improvements for cl-flet akater
2021-09-26 6:54 ` Lars Ingebrigtsen
2021-09-26 12:04 ` akater
2021-09-26 12:36 ` Lars Ingebrigtsen
2021-10-03 3:51 ` Stefan Monnier
2021-10-07 5:02 ` akater
2021-10-07 18:23 ` Stefan Monnier
2021-11-03 12:59 ` akater
2021-11-09 20:37 ` Stefan Monnier
2021-10-09 5:33 ` akater
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=87mtncjlww.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nuclearspace@gmail.com \
--cc=rms@gnu.org \
/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.