From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 50219@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#50219: 28.0.50; Provide better errors when trying to specialize on optional args in generic methods
Date: Fri, 27 Aug 2021 02:34:49 +0200 [thread overview]
Message-ID: <87bl5ju3me.fsf@gnus.org> (raw)
In-Reply-To: <87k0k7by2w.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 26 Aug 2021 16:11:51 -0700")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> - the manual section on "Generic Functions" could say explicitly that
> you can't specialize on optional arguments
> - `eval'ling the `defmethod' form above could raise an error directly
> - the compiler could say more explicitly what the problem is
>
> I'd favor all three of these changes!
Me, too.
> Happy to implement what I can (maybe not the compiler part).
I've added Stefan to the CCs; perhaps he has some comments.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-08-27 0:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 23:11 bug#50219: 28.0.50; Provide better errors when trying to specialize on optional args in generic methods Eric Abrahamsen
2021-08-27 0:34 ` Lars Ingebrigtsen [this message]
2021-08-27 1:31 ` Eric Abrahamsen
2021-08-28 14:15 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-28 16:02 ` Lars Ingebrigtsen
2021-08-28 16:42 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-28 17:12 ` Lars Ingebrigtsen
2021-08-28 17:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-28 17:49 ` Lars Ingebrigtsen
2021-08-29 0:47 ` Eric Abrahamsen
2021-08-29 11:10 ` Michael Heerdegen
2021-08-29 15:41 ` Eric Abrahamsen
2021-08-29 19:16 ` Michael Heerdegen
2021-08-30 3:33 ` Eric Abrahamsen
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=87bl5ju3me.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=50219@debbugs.gnu.org \
--cc=eric@ericabrahamsen.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).