From: Marco Antoniotti <marcoxa@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: brubar.cs@gmail.com, monnier@iro.umontreal.ca,
70597-done@debbugs.gnu.org
Subject: bug#70597: Problem in pcase-let?
Date: Sat, 4 May 2024 14:06:45 +0200 [thread overview]
Message-ID: <CAKmY7cUUFocQGkPoesXLjcs1fdO3JDYkT-Ff9BThDpx2f=8Qeg@mail.gmail.com> (raw)
In-Reply-To: <861q6hhks0.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
Hi
sorry, but I do not think that the current doc string and/or the manual
explains the situation.
And it looks like this is a recurring misunderstanding by the users.
Just adding the example would clarify things.
All the best
MA
On Sat, May 4, 2024 at 1:35 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Marco Antoniotti <marcoxa@gmail.com>
> > Date: Thu, 2 May 2024 13:06:58 +0200
> > Cc: Stefan Monnier <monnier@iro.umontreal.ca>, brubar.cs@gmail.com,
> 70597@debbugs.gnu.org
> >
> > it's your call. But please change the doc string to clarify that
> pcase-let does not do "symbol equality" pattern
> > matching, but only structural matching. Adding an example like the
> following will help.
> >
> > (pcase-let ((`(foo ,x 23 ,y) '(bar 11 baz 22))) (list x y))
>
> This is already explained in the ELisp manual, and the doc string
> already says
>
> Each EXP should match its respective PATTERN (i.e. be of structure
> compatible to PATTERN)
>
> So I don't think we need to do anything else here, and I'm closing
> this bug.
>
--
Marco Antoniotti
Somewhere over the Rainbow
[-- Attachment #2: Type: text/html, Size: 1960 bytes --]
next prev parent reply other threads:[~2024-05-04 12:06 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
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 [this message]
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='CAKmY7cUUFocQGkPoesXLjcs1fdO3JDYkT-Ff9BThDpx2f=8Qeg@mail.gmail.com' \
--to=marcoxa@gmail.com \
--cc=70597-done@debbugs.gnu.org \
--cc=brubar.cs@gmail.com \
--cc=eliz@gnu.org \
--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).