From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: pcase-dolist
Date: Fri, 10 Jul 2015 14:51:51 -0400 [thread overview]
Message-ID: <jwvegkfoniv.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87a8v53wll.fsf@web.de> (Michael Heerdegen's message of "Thu, 09 Jul 2015 22:27:34 +0200")
> Good argument. OTOH, if you _want_ to distinguish e.g. a two from a
> three element list, you will have to use something like `(,a ,b . ,r)
> and test whether r is nil.
No: pcase-let is for "destructuring", not for "distinguishing".
IOW if you want "to distinguish e.g. a two from a three element list"
you want to use `pcase'.
> Mmh. Anyway, pcase and pcase-let should
> at least behave the same at the end I think...
Then what would be the benefit of having `pcase-let'?
Stefan
next prev parent reply other threads:[~2015-07-10 18:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 12:20 pcase-dolist Michael Heerdegen
2015-07-08 13:54 ` pcase-dolist Stefan Monnier
2015-07-08 17:32 ` pcase-dolist Michael Heerdegen
2015-07-08 18:26 ` pcase-dolist Tassilo Horn
2015-07-08 21:27 ` pcase-dolist Stefan Monnier
2015-07-09 6:05 ` pcase-dolist Tassilo Horn
2015-07-09 9:55 ` pcase-dolist Thierry Volpiatto
2015-07-09 10:17 ` pcase-dolist Tassilo Horn
2015-07-09 12:19 ` pcase-dolist Thierry Volpiatto
2015-07-09 13:34 ` pcase-dolist Tassilo Horn
2015-07-09 13:40 ` pcase-dolist Thierry Volpiatto
2015-07-09 19:26 ` pcase-dolist Stefan Monnier
2015-07-09 20:27 ` pcase-dolist Michael Heerdegen
2015-07-10 18:51 ` Stefan Monnier [this message]
2015-10-12 11:27 ` pcase-setq (was: pcase-dolist) Michael Heerdegen
2015-10-12 11:54 ` pcase-setq Michael Heerdegen
2015-10-12 12:01 ` pcase-setq (was: pcase-dolist) Nicolas Petton
2015-10-12 12:36 ` pcase-setq Michael Heerdegen
2015-10-12 12:49 ` Semantic of pcase `seq' and `map' patterns (was: pcase-setq) Michael Heerdegen
2015-10-12 13:41 ` Semantic of pcase `seq' and `map' patterns Michael Heerdegen
2015-10-12 13:55 ` Nicolas Petton
2015-10-12 14:02 ` Michael Heerdegen
2015-10-17 12:21 ` Michael Heerdegen
2015-10-17 13:31 ` Nicolas Petton
2015-10-12 13:50 ` Semantic of pcase `seq' and `map' patterns (was: pcase-setq) Nicolas Petton
2015-10-13 0:59 ` pcase-setq Stefan Monnier
2015-10-13 13:52 ` pcase-setq Michael Heerdegen
2015-10-13 14:02 ` pcase-setq Michael Heerdegen
2015-10-13 15:52 ` pcase-setq Michael Heerdegen
[not found] ` <jwvfv1eboo8.fsf-monnier+emacs@gnu.org>
[not found] ` <87d1wh36as.fsf@web.de>
2015-10-14 15:49 ` pcase-setq Stefan Monnier
2015-07-10 14:44 ` pcase-dolist Tassilo Horn
2015-07-10 19:04 ` pcase-dolist Stefan Monnier
2015-07-08 19:44 ` pcase-dolist Artur Malabarba
2015-07-08 20:50 ` pcase-dolist Michael Heerdegen
-- strict thread matches above, loose matches on Subject: below --
2014-07-11 10:35 pcase-dolist Sebastian Wiesner
2014-07-11 13:47 ` pcase-dolist Stefan Monnier
2014-07-11 13:50 ` pcase-dolist Sebastian Wiesner
2014-07-11 14:14 ` pcase-dolist Stefan Monnier
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=jwvegkfoniv.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.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 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).