From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: brubar.cs@gmail.com, marcoxa@gmail.com, 70597@debbugs.gnu.org
Subject: bug#70597: Problem in pcase-let?
Date: Sun, 28 Apr 2024 13:18:46 +0300 [thread overview]
Message-ID: <86mspdu6wp.fsf@gnu.org> (raw)
In-Reply-To: <87frv5ls0v.fsf@localhost> (message from Ihor Radchenko on Sun, 28 Apr 2024 10:07:28 +0000)
> Cc: Marco Antoniotti <marcoxa@gmail.com>, 70597@debbugs.gnu.org
> From: Ihor Radchenko <yantar92@posteo.net>
> Date: Sun, 28 Apr 2024 10:07:28 +0000
>
> Bruno Barbier <brubar.cs@gmail.com> writes:
>
> > So, you would prefer for pcase-let to always signal an error if a
> > pattern doesn't match. It makes sense.
> >
> > And it looks like the issue has already been raised: see bug#19670.
> > (see https://debbugs.gnu.org/cgi/bugreport.cgi?bug=19670)
>
> Also, see https://debbugs.gnu.org/cgi/bugreport.cgi?bug=68509
Adding Stefan, in case he has comments.
next prev parent reply other threads:[~2024-04-28 10:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 18:00 bug#70597: Problem in pcase-let? Marco Antoniotti
2024-04-27 16:11 ` Bruno Barbier
2024-04-27 22:28 ` Marco Antoniotti
2024-04-28 10:01 ` Bruno Barbier
2024-04-28 10:07 ` Ihor Radchenko
2024-04-28 10:18 ` Eli Zaretskii [this message]
2024-04-28 15:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-28 15:38 ` Marco Antoniotti
2024-04-28 17:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-28 18:22 ` Marco Antoniotti
2024-04-28 21:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-02 9:23 ` Eli Zaretskii
2024-05-02 11:06 ` Marco Antoniotti
2024-05-04 11:35 ` Eli Zaretskii
2024-05-04 12:06 ` Marco Antoniotti
2024-05-04 15:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-05 8:49 ` Marco Antoniotti
2024-05-04 15:23 ` 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=86mspdu6wp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70597@debbugs.gnu.org \
--cc=brubar.cs@gmail.com \
--cc=marcoxa@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).