From: Stefan Kangas <stefankangas@gmail.com>
To: "Pierre L. Nageoire" <devel@pollock-nageoire.net>, 56596@debbugs.gnu.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#56596: 29.0.50; void-variable cl--nm
Date: Sat, 16 Jul 2022 15:42:59 -0700 [thread overview]
Message-ID: <CADwFkm=7b8su35dC6+6MnEafeYFrqjTiBqykHY-ta2_BomLJyw@mail.gmail.com> (raw)
In-Reply-To: <8735f18mxg.fsf@pollock-nageoire.net>
"Pierre L. Nageoire" <devel@pollock-nageoire.net> writes:
> Caused by following code
>
> (require 'eieio)
>
> (defclass raw-mother () ())
>
> (cl-defmethod I ((m raw-mother))
> (format "the mother"))
>
> (cl-defmethod hello ((m raw-mother))
> (message "I am %s" (I m)))
>
> (hello (raw-mother))
>
> (defclass raw-daughter (raw-mother) ())
>
> (cl-defmethod I ((d raw-daughter))
> (format "the daughter of %s"
> (cl-call-next-method)))
>
>
> (hello (raw-daughter))
>
>
>
> But only since last update from git repos. With an emacs version updated
> in march approximately no problem.
6f973faa912a5ac1ba643c6f5deb0c02baa0ba6d is the first bad commit
commit 6f973faa912a5ac1ba643c6f5deb0c02baa0ba6d
Author: Stefan Monnier <monnier@iro.umontreal.ca>
Date: Wed Mar 30 13:54:56 2022 -0400
cl-generic: Use OClosures for `cl--generic-isnot-nnm-p`
Rewrite the handling of `cl-no-next-method` to get rid of the hideous
hack used in `cl--generic-isnot-nnm-p` and also to try and move
some of the cost to the construction of the effective method rather
than its invocation. This speeds up method calls measurably when
there's a `cl-call-next-method` in the body.
prev parent reply other threads:[~2022-07-16 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 8:46 bug#56596: 29.0.50; void-variable cl--nm Pierre L. Nageoire
2022-07-16 11:12 ` Lars Ingebrigtsen
2022-07-16 18:06 ` Pierre L. Nageoire
2022-07-16 23:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 3:36 ` Pierre L. Nageoire
2022-07-16 22:42 ` Stefan Kangas [this message]
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='CADwFkm=7b8su35dC6+6MnEafeYFrqjTiBqykHY-ta2_BomLJyw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=56596@debbugs.gnu.org \
--cc=devel@pollock-nageoire.net \
--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).