From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: pcase-if-let?
Date: Thu, 29 Mar 2018 07:24:59 +0200 [thread overview]
Message-ID: <87woxvh2s4.fsf@web.de> (raw)
In-Reply-To: <jwvd0znqykm.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Thu, 29 Mar 2018 00:53:29 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> FWIW, I'm a bit worried about this case: it's not like this pcase-if
> is a "pcase version of some existing construct", so if we ever want to
> get rid of the "pcase-" prefix on it, we'll have to invent a new name
> for it.
True. But "pif" sounds too funny...we need to find a different name.
> PS: Regarding the "unorthodox" shape of the pcase construct, you could
> generate an expression of the form (pcase (list E1 E2 ...) ((list P1 P2
> ...) THEN) (_ ELSE)).
What's `list' - a new pattern type? If you write it like this, it looks
like parallel matching of the Pi patterns, though we need to match in
order for i=1,...
Michael.
next prev parent reply other threads:[~2018-03-29 5:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 23:20 pcase-if-let? Michael Heerdegen
2018-03-28 23:54 ` pcase-if-let? Davis Herring
2018-03-29 0:21 ` pcase-if-let? Michael Heerdegen
2018-03-29 3:46 ` pcase-if-let? Michael Heerdegen
2018-03-29 4:14 ` pcase-if-let? Drew Adams
2018-03-29 4:39 ` pcase-if-let? Michael Heerdegen
2018-03-29 4:49 ` pcase-if-let? Drew Adams
2018-03-29 4:53 ` pcase-if-let? Stefan Monnier
2018-03-29 5:24 ` Michael Heerdegen [this message]
2018-03-29 11:59 ` pcase-if-let? Stefan Monnier
2018-03-30 1:52 ` pcase-if-let? Michael Heerdegen
2018-03-30 4:07 ` pcase-if-let? Drew Adams
2018-03-30 5:09 ` pcase-if-let? Michael Heerdegen
2018-03-30 15:07 ` pcase-if-let? Drew Adams
2018-03-30 23:22 ` pcase-if-let? Michael Heerdegen
2018-04-17 20:26 ` pcase-if-let? Nathan Moreau
2018-04-17 21:04 ` pcase-if-let? Michael Heerdegen
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=87woxvh2s4.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=emacs-devel@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 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.