From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Why is FUNC in cl-callf not allowed to be an expression?
Date: Thu, 16 May 2019 16:37:26 +0200 [thread overview]
Message-ID: <875zqabh3t.fsf@web.de> (raw)
In-Reply-To: <jwvd0kih7yz.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 16 May 2019 09:12:40 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Hmm... that's indeed what I see, but I haven't yet understood why that
> is (or rather, why that doesn't happen to your gv-ad-hoc-place). I
> guess that qualifies as a bug in gv-synthetic-place (not that it
> matters too much: I can't find a single use of it).
Well, let's see:
;; works:
(let ((l '(0)))
(cl-symbol-macrolet ((p (gv-synthetic-place (car l) (lambda (v) `(setcar l ,v)))))
(setf p 1))
l) ;; ==> (1)
;; dosn't work:
(let ((l '((0))))
(let ((cl (car l)))
(cl-symbol-macrolet ((p (gv-synthetic-place cl (lambda (v) `(setcar cl ,v)))))
(setf p 1)))
l) ;; ==> ((0))
;; but this works
(let ((l '((0))))
(let ((cl (car l)))
(setf (gv-synthetic-place cl (lambda (v) `(setcar cl ,v))) 1))
l) ;; ((1))
The problem in the second case is that `cl-symbol-macrolet' is too
eager: it also macroexpands the symbol expansion `p' inside the `setf',
i.e. it expands the `gv-synthetic-place' macro call, to just `cl', so
you get (setf cl 1).
That just doesn't happen to my version since it's a function instead of
a macro (and the compiler macro seems to be applied later).
Any suggestions?
Michael.
next prev parent reply other threads:[~2019-05-16 14:37 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 21:52 Why is FUNC in cl-callf not allowed to be an expression? Michael Heerdegen
2019-05-10 0:47 ` Stefan Monnier
2019-05-10 11:32 ` Michael Heerdegen
2019-05-10 13:28 ` Stefan Monnier
2019-05-10 14:19 ` Stefan Monnier
2019-05-10 14:22 ` Stefan Monnier
2019-05-10 15:18 ` Michael Heerdegen
2019-05-13 16:47 ` Stefan Monnier
2019-05-14 12:36 ` Michael Heerdegen
2019-05-14 23:32 ` Michael Heerdegen
2019-05-15 2:02 ` Stefan Monnier
2019-05-15 16:38 ` Michael Heerdegen
2019-05-15 17:19 ` Michael Heerdegen
2019-05-16 2:18 ` Michael Heerdegen
2019-05-16 13:12 ` Stefan Monnier
2019-05-16 14:37 ` Michael Heerdegen [this message]
2019-05-16 15:09 ` Michael Heerdegen
2019-05-16 19:34 ` Stefan Monnier
2019-05-16 21:46 ` Michael Heerdegen
2019-05-16 23:06 ` Stefan Monnier
2019-05-17 22:53 ` Michael Heerdegen
2019-05-18 14:09 ` Stefan Monnier
2019-05-20 23:25 ` Michael Heerdegen
2019-05-21 2:01 ` Stefan Monnier
2019-05-21 2:47 ` Michael Heerdegen
2019-05-21 10:16 ` Noam Postavsky
2019-05-21 16:38 ` Michael Heerdegen
2019-05-21 17:38 ` Stefan Monnier
2019-05-21 7:26 ` Andy Moreton
2019-05-23 23:02 ` Michael Heerdegen
2019-05-22 1:00 ` Michael Heerdegen
2019-05-23 1:50 ` Michael Heerdegen
2019-05-23 3:38 ` Stefan Monnier
2019-05-23 23:38 ` Michael Heerdegen
2019-05-24 15:29 ` Stefan Monnier
2019-05-28 19:54 ` Michael Heerdegen
2019-05-27 0:20 ` Michael Heerdegen
2019-05-29 17:02 ` Stefan Monnier
2019-05-15 19:17 ` Michael Heerdegen
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=875zqabh3t.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).