From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, 50219@debbugs.gnu.org
Subject: bug#50219: 28.0.50; Provide better errors when trying to specialize on optional args in generic methods
Date: Sat, 28 Aug 2021 19:49:11 +0200 [thread overview]
Message-ID: <87sfyth33c.fsf@gnus.org> (raw)
In-Reply-To: <jwvy28lii82.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 28 Aug 2021 13:41:48 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> The default value part of args in Common lisp arglists is an
> *expression*, so (b string) just means that `b` should take the value of
> the `string` variable.
>
> The best I can see (if we keep the CL arglist feature) is to try and see
> if that expression looks like a valid CLOS specializer and if so emit
> a warning about possible confusion.
Yes, that's what I tried to say. :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-08-28 17:49 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
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 [this message]
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=87sfyth33c.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).