From: Wing Hei Chan <whmunkchan@outlook.com>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: "56739@debbugs.gnu.org" <56739@debbugs.gnu.org>
Subject: bug#56739: 29.0.50; `cl-psetq' and `cl-psetf' fail to recognize symbol macros
Date: Sat, 9 Sep 2023 08:03:42 +0000 [thread overview]
Message-ID: <1068bf85-4fd0-43a1-9aba-71d71312c4f1@outlook.com> (raw)
In-Reply-To: <f49326d6-85e2-4fed-83ae-815a82cefe30@outlook.com>
Resending this message as I didn't send it to the thread.
> Afaik, *left-hand* side symbol macros are all handled correctly:
>
> - `setq' is handled by `cl-symbol-macrolet' itself;
> - `setf' expands symbol macros as needed;
> - `cl-setq' and `cl-setf' expand to `setf'.
>
> The original bug is about *right-hand* side symbol macros, namely that
> `cl-setq' and `cl-setf' can introduce an unsound optimization in such
> cases. In fact, I'm not sure this optimization is needed anymore (see
> Stefan's comment). The simplest way to fix the bug is to remove the
> optimization, but I'll leave the decision to more knowledgeable people.
next prev parent reply other threads:[~2023-09-09 8:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 12:12 bug#56739: 29.0.50; `cl-psetq' and `cl-psetf' fail to recognize symbol macros Wing Hei Chan
2022-08-02 2:41 ` Michael Heerdegen
2022-08-02 23:59 ` Michael Heerdegen
2022-08-03 0:20 ` Michael Heerdegen
2022-09-05 19:14 ` Lars Ingebrigtsen
2022-09-06 1:29 ` Michael Heerdegen
2022-09-06 2:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-07 18:31 ` Stefan Kangas
2023-09-08 3:07 ` Michael Heerdegen
2023-09-09 6:12 ` Michael Heerdegen
2023-09-09 7:08 ` Gerd Möllmann
[not found] ` <f49326d6-85e2-4fed-83ae-815a82cefe30@outlook.com>
2023-09-09 8:03 ` Wing Hei Chan [this message]
2023-09-09 9:24 ` Gerd Möllmann
2023-09-09 15:42 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09 16:33 ` Gerd Möllmann
2022-09-06 2:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=1068bf85-4fd0-43a1-9aba-71d71312c4f1@outlook.com \
--to=whmunkchan@outlook.com \
--cc=56739@debbugs.gnu.org \
--cc=gerd.moellmann@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.