From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Why is FUNC in cl-callf not allowed to be an expression? Date: Thu, 16 May 2019 09:12:40 -0400 Message-ID: References: <874l631ek1.fsf@web.de> <87pnoqtuhm.fsf@web.de> <87r2961gox.fsf@web.de> <87mujohasa.fsf@web.de> <87a7fn3c6c.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="196350"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 16 15:20:28 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hRGJ4-000ouY-L8 for ged-emacs-devel@m.gmane.org; Thu, 16 May 2019 15:20:22 +0200 Original-Received: from localhost ([127.0.0.1]:56758 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hRGJ3-00083j-Fr for ged-emacs-devel@m.gmane.org; Thu, 16 May 2019 09:20:21 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:35794) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hRGBz-0003fz-8g for emacs-devel@gnu.org; Thu, 16 May 2019 09:13:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hRGBw-0000FF-8C for emacs-devel@gnu.org; Thu, 16 May 2019 09:13:03 -0400 Original-Received: from [195.159.176.226] (port=42506 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hRGBw-0000Dh-2L for emacs-devel@gnu.org; Thu, 16 May 2019 09:13:00 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1hRGBn-000gMG-KN for emacs-devel@gnu.org; Thu, 16 May 2019 15:12:51 +0200 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:lw0Hvd2D221lvuzoThYRFdBq3F4= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:236577 Archived-At: > (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