From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Michael Heerdegen <michael_heerdegen@web.de>
Cc: 31350@debbugs.gnu.org
Subject: bug#31350: 27.0; `pcase' message: "Redundant pcase pattern"
Date: Sun, 4 Oct 2020 10:45:54 -0700 (PDT) [thread overview]
Message-ID: <e4a66b55-ba0f-486b-8015-e640e26f86c6@default> (raw)
In-Reply-To: <87v9fqrsvf.fsf@gnus.org>
> Perhaps the warning should be more explicit? "Redundant pcase pattern"
> is obvious if you already know what it means, but if you don't, it's
> not. :-) So something like "pcase pattern shadowed by previous pcase
> pattern" or something along those lines?
That's a start. But as I said:
And even if a user (somehow) understands that later
cases are made redundant by earlier ones, how to tell
which earlier ones are implicated?
Just saying that some previous pcase pattern makes
this one redundant doesn't tell you which previous
pattern that does that. It should.
next prev parent reply other threads:[~2020-10-04 17:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 0:48 bug#31350: 27.0; `pcase' message: "Redundant pcase pattern" Drew Adams
2018-05-03 1:16 ` Michael Heerdegen
2018-05-03 18:18 ` Drew Adams
2020-08-20 15:55 ` Lars Ingebrigtsen
2020-10-03 22:52 ` Michael Heerdegen
2020-10-03 22:58 ` Drew Adams
2020-10-04 1:37 ` Michael Heerdegen
2020-10-04 2:06 ` Drew Adams
2020-10-04 14:03 ` Lars Ingebrigtsen
2020-10-04 17:45 ` Drew Adams [this message]
2020-10-04 23:55 ` Michael Heerdegen
2020-10-04 23:54 ` Michael Heerdegen
2020-12-12 13:24 ` Lars Ingebrigtsen
2020-12-12 17:00 ` Drew Adams
2020-12-12 19:01 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4a66b55-ba0f-486b-8015-e640e26f86c6@default \
--to=drew.adams@oracle.com \
--cc=31350@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.