unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: akater <nuclearspace@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Some improvements for cl-flet
Date: Thu, 07 Oct 2021 14:23:36 -0400	[thread overview]
Message-ID: <jwvily8btls.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87pmshqvfk.fsf@gmail.com> (akater's message of "Thu, 07 Oct 2021 05:02:23 +0000")

>> Maybe it might be worthwhile splitting it into 2 or 3 patches so as to
>> better see how we got to the level of complexity.
>> See more comments below.
>
> Local setfs certainly can be added later (or simply dropped, until
> better times).  It will simplify the patch.

I'm fine adding it now, but I'd like to see the intermediate steps to
better understand what is due to what.

>> Why do we have/need this?  Does it work with other things that use
>> gv-places, like `push`, `pop`, `cl-callf`, ...?  If so, how?
>> If not, then we need another approach which does.
>
> I added support for local setfs mostly

I understand why we want support for local setf functions.
My question was why do we need the code I referred to in order to
implement that feature.

The patch below seems to work for me.

>> I thought handling `cl-flet` of (setf foo) would amount to calling
>> `gv-setter` to get the symbol corresponding to `(setf foo)` and then
>> c-flet-binding that symbol instead of `(setf foo).
> At the very least, gv-setter will fail for local (setf car) and so on.
> I don't know how cl-flet should treat such things (in Common Lisp it's
> UB) but I saw that cl-flet performs local redefinition of car just fine
> so I followed suit.

I'd also consider such a (setf car) as UB, but as for how does it behave
in practice: basically `car` has a `gv-expander` and those take
precedence over a (setf car) function.

>>> +(defun cl--expand-flet (env body &rest flet-expanders-plist)
>>> +  "Return a form equivalent to `(cl-flet ,bindings BODY)
>>> +where bindings correspond to FLET-EXPANDERS-PLIST as described below.
>>> +
>>> +ENV should be macroexpansion environment
>>> +to be augmented with some definitions from FLET-EXPANDERS-PLIST
>>> +to then expand forms in BODY with.
>>> +
>>> +FLET-EXPANDERS-PLIST should be a plist
>>> +where keys are function names
>>> +and values are 0-argument lambdas
>>> +to be called if the corresponding function name is encountered
>>> +in BODY and then only (that is, at most once).
>>
>> Why "at most once"?
>
> We don't want to end up calling different functions in different
> instances of local function calls which share the same name within a
> single cl-flet form, for whatever unforseeable reason this might happen
> (like poorly written flet-expander or poorly written exp in (func exp)).

The question is why enforce this here rather than elsewhere.
It restricts the possible uses of `cl--expand-flet` and I get the
impression that it doesn't save us any significant complexity in the
callers (it saves us less complexity there than it costs us here).
E.g. in:

> (cl--expand-flet macroenv (cdr parsed-body)
>   'cl-call-next-method (lambda () (push cnm uses-cnm)
>                          (list nil cnm))
>   'cl-next-method-p (lambda () (push nmp uses-cnm)
>                       (list nil nmp)))

If the functions where called multiple times rather than "at
most once", we'd just replace the `push` with `cl-pushnew`.

But that's a very minor cosmetic detail.  Either way works, I was just
curious why you did it this way.


        Stefan


diff --git a/lisp/emacs-lisp/cl-macs.el b/lisp/emacs-lisp/cl-macs.el
index 1852471bcbb..ad0477e3b68 100644
--- a/lisp/emacs-lisp/cl-macs.el
+++ b/lisp/emacs-lisp/cl-macs.el
@@ -2030,7 +2030,10 @@ cl-flet
   (let ((binds ()) (newenv macroexpand-all-environment))
     (dolist (binding bindings)
       (let ((var (make-symbol (format "--cl-%s--" (car binding))))
+            (fname (car binding))
             (args-and-body (cdr binding)))
+        (if (eq (car-safe fname) 'setf)
+            (setq fname (gv-setter (cadr fname))))
         (if (and (= (length args-and-body) 1) (symbolp (car args-and-body)))
             ;; Optimize (cl-flet ((fun var)) body).
             (setq var (car args-and-body))
@@ -2038,7 +2041,7 @@ cl-flet
                               (car args-and-body)
                             `(cl-function (lambda . ,args-and-body))))
                 binds))
-	(push (cons (car binding)
+	(push (cons fname
                     (lambda (&rest args)
                       (if (eq (car args) cl--labels-magic)
                           (list cl--labels-magic var)




  reply	other threads:[~2021-10-07 18:23 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
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 [this message]
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

  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=jwvily8btls.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=nuclearspace@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 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).