From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Jim Porter <jporterbugs@gmail.com>, 68509@debbugs.gnu.org
Subject: bug#68509: 30.0.50; pcase-dolist matches backquote pattern incorrectly
Date: Tue, 20 Feb 2024 09:35:59 -0500 [thread overview]
Message-ID: <jwvil2jqkq2.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87o7cbz21n.fsf@localhost> (Ihor Radchenko's message of "Tue, 20 Feb 2024 13:40:52 +0000")
> What about adding extra option/keyword and also showing a runtime
> warning when pcase-dolist/pcase-let encounter something that does not
> match the pattern?
In the current use of those primitives, it's routine/normal/common for
a pattern like `(,a ,b) to encounter lists of different length than 2,
so a warning should be emitted only if specifically requested via an
option/keyword.
I think it would be OK to emit a warning (even if not specifically
requested via an option/keyword) when a value like (help . me) fails to
match `(a . ,b), but as mentioned I don't know a good way to distinguish
those two kinds of cases.
Stefan
next prev parent reply other threads:[~2024-02-20 14:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 15:07 bug#68509: 30.0.50; pcase-dolist matches backquote pattern incorrectly Ihor Radchenko
2024-01-16 16:52 ` Jim Porter
2024-01-16 18:43 ` Ihor Radchenko
2024-02-19 10:05 ` Ihor Radchenko
2024-02-19 12:59 ` Eli Zaretskii
2024-02-19 15:53 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-19 18:14 ` Ihor Radchenko
2024-02-20 2:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-20 13:40 ` Ihor Radchenko
2024-02-20 14:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-02-20 15:16 ` Ihor Radchenko
2024-02-20 17:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-21 11:23 ` Ihor Radchenko
2024-02-21 14:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-23 14:05 ` Ihor Radchenko
2024-02-23 14:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-24 13:28 ` Ihor Radchenko
2024-02-24 14:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-19 15:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-19 18:16 ` Ihor Radchenko
2024-02-20 2:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=jwvil2jqkq2.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=68509@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=yantar92@posteo.net \
/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).