Re: Why is FUNC in cl-callf not allowed to be an expression?

[Stefan Monnier]

> (defun gv-ad-hoc-place (val _setter)
>   (declare (compiler-macro (lambda (_) val))
>            (gv-expander funcall))
>   val)
[...]
> Note that `gv-synthetic-place' can't be used here because in setf it
> would just expand to (setq val ...) with val being the let-bound symbol
> in the implementation, instead of something setf'ing the PLACE.

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).


        Stefan