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] Improve detection of local function calls in methods
Date: Thu, 02 Sep 2021 14:34:28 -0400	[thread overview]
Message-ID: <jwvv93ig7c5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87zgt0sdbg.fsf@gmail.com> (akater's message of "Sun, 29 Aug 2021 11:25:07 +0000")

> I don't know if all this is appropriate style; I provide patches this
> way in the hope it's acceptable.

Yes, that's very nice, thank you.

> @@ -377,24 +377,51 @@ defun cl--generic-lambda (args body)
>        ;; destructuring args, `declare' and whatnot).
>        (pcase (macroexpand fun macroenv)
>          (`#'(lambda ,args . ,body)
> -         (let* ((parsed-body (macroexp-parse-body body))
> +         (let* ((parsed-body (macroexp-parse-body body)) uses-cnm
>                  (cnm (make-symbol "cl--cnm"))
>                  (nmp (make-symbol "cl--nmp"))
> -                (nbody (macroexpand-all
> -                        `(cl-flet ((cl-call-next-method ,cnm)
> -                                   (cl-next-method-p ,nmp))
> -                           ,@(cdr parsed-body))
> -                        macroenv))
> -                ;; FIXME: Rather than `grep' after the fact, the
> -                ;; macroexpansion should directly set some flag when cnm
> -                ;; is used.
> +                (nbody
> +                 ;; We duplicate the code from `cl-flet' augmenting it
> +                 ;; with `cl-pushnew' forms to record the presence of
> +                 ;; `cl-call-next-method', `cl-next-method-p'.
> +                 ;; It would be better to avoid code duplication
> +                 ;; but it's not clear how to do that reasonably enough.
> +                 (let ((newenv
> +                        (cons `(cl-call-next-method
> +                                .
> +                                ,(lambda (&rest args)
> +                                   (cl-pushnew cnm uses-cnm :test #'eq)
> +                                   (if (eq (car args) cl--labels-magic)
> +                                       (list cl--labels-magic cnm)
> +                                     `(funcall ,cnm ,@args))))
> +                              (cons `(cl-next-method-p
> +                                      .
> +                                      ,(lambda (&rest args)
> +                                         (cl-pushnew nmp uses-cnm :test #'eq)
> +                                         (if (eq (car args) cl--labels-magic)
> +                                             (list cl--labels-magic nmp)
> +                                           `(funcall ,nmp ,@args))))
> +                                    macroenv))))
> +                   (macroexpand-all
> +                    `(progn ,@(cdr parsed-body))
> +                    ;; Don't override lexical-let's macro-expander
> +                    (if (assq 'function newenv) newenv
> +                      (cons (cons 'function
> +                                  (lambda (f)
> +                                    (cl-case f
> +                                      (cl-call-next-method
> +                                       (cl-pushnew cnm uses-cnm :test #'eq))
> +                                      (cl-next-method-p
> +                                       (cl-pushnew nmp uses-cnm :test #'eq)))
> +                                    (cl--labels-convert f)))
> +                            newenv)))))

Hmm... the reason why I didn't do that (when I wrote the comment
instead), is that I find this duplication ugly.

I think "the right way" would be for the `cl-flet` implementation to use
a `cl--expand-flet` function returning which functions are used
and which aren't.

Then we could use it here without such duplication, *and* we could use
it in `cl-flet` to emit warnings about unused functions.

WDYT?


        Stefan




  reply	other threads:[~2021-09-02 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27 21:41 [PATCH] Improve detection of local function calls in methods akater
2021-08-27 22:59 ` Stefan Monnier
2021-08-29 11:25   ` akater
2021-09-02 18:34     ` Stefan Monnier [this message]
2021-09-10  6:25       ` akater
2021-09-10 15:49         ` Stefan Monnier

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