all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Anaphoric macros: increase visibility
Date: Mon, 16 Jan 2017 11:44:13 +0900 (JST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1701161141160.7787@calancha-pc> (raw)
In-Reply-To: <jwv60lg8i0k.fsf-monnier+gmane.emacs.devel@gnu.org>



On Sun, 15 Jan 2017, Stefan Monnier wrote:

> Tino writes:
>>> (pcase-let ((`(,a ,b) '(1 2 3)))
>>> (list a b))
>>> ==> (1 2)
>>> although the pattern doesn't match.
>> I can be bitten with that pitfall as well.
>
> I think the problem is in the name: it really should be called just `let`.
> It does not do any *match*, instead the pcase pattern is only used to
> specify how to *extract* the data we want.
I see.  Then, `pcase-let' is somehow similar than `-let' in dash.el.



  reply	other threads:[~2017-01-16  2:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13  8:39 Anaphoric macros: increase visibility Tino Calancha
2017-01-13 19:48 ` Michael Heerdegen
2017-01-14  2:30   ` Rolf Ade
2017-01-14  2:48     ` Rolf Ade
2017-01-14  3:03     ` Noam Postavsky
2017-01-14  4:13       ` Richard Copley
2017-01-14  5:27   ` Tino Calancha
2017-01-15  0:39     ` Michael Heerdegen
2017-01-15  2:24       ` On the naming/behavior of {if, when}-let (was Re: Anaphoric macros: increase visibility) Mark Oteiza
2017-01-15  2:26       ` Anaphoric macros: increase visibility Michael Heerdegen
2017-01-15 10:24       ` Tino Calancha
2017-01-15 15:32         ` Stefan Monnier
2017-01-16  2:44           ` Tino Calancha [this message]
2017-01-16  3:59             ` Stefan Monnier
2017-01-14  6:25   ` Dmitri Paduchikh
2017-01-14  7:56     ` Tino Calancha
2017-01-14 10:15       ` Dmitri Paduchikh
2017-01-15  0:29         ` Michael Heerdegen
2017-01-15  2:03           ` Dmitri Paduchikh
2017-01-15  2:16             ` 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=alpine.DEB.2.20.1701161141160.7787@calancha-pc \
    --to=tino.calancha@gmail.com \
    --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.