unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: Dmitry Gutov <dgutov@yandex.ru>, Alan Mackenzie <acm@muc.de>,
	 emacs-devel@gnu.org
Subject: Re: A protest against pcase, pcase-let, pcase-let*
Date: Wed, 01 Apr 2015 00:46:17 -0700	[thread overview]
Message-ID: <551BA249.9020205@dancol.org> (raw)
In-Reply-To: <551AF4AA.3040300@yandex.ru>

[-- Attachment #1: Type: text/plain, Size: 811 bytes --]

On 03/31/2015 12:25 PM, Dmitry Gutov wrote:
> On 03/31/2015 09:00 PM, Alan Mackenzie wrote:
> 
>> OK, maybe pcase itself has a page in the elisp manual, but this page is
>> very difficult to understand, certainly for me.  I have attempted quite
>> a lot of times to make sense of it, and failed.
> 
> I think it's pretty nice. It provides pattern matching, as well as
> destructuring (something that previously required the use of cl-lib), in
> a concise and performant way.
> 
> The docs can look a bit dense at first, but after reading them carefully
> and experimenting a bit, I'm sure most people can get a hang of it.

pcase is really an excellent tool. The documentation is better for
reference than for learning how to use it, though. Good thing Emacs is
full of pcase examples now.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-04-01  7:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 18:00 A protest against pcase, pcase-let, pcase-let* Alan Mackenzie
2015-03-31 18:29 ` John Wiegley
2015-04-18  1:47   ` Ted Zlatanov
2015-03-31 19:25 ` Dmitry Gutov
2015-04-01  7:46   ` Daniel Colascione [this message]
2015-04-01  9:59 ` Phillip Lord
2015-04-01 12:04   ` Nic Ferrier
2015-04-01 12:16     ` Dmitry Gutov
2015-04-01 13:53     ` Stefan Monnier
2015-04-02  7:19   ` Richard Stallman

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=551BA249.9020205@dancol.org \
    --to=dancol@dancol.org \
    --cc=acm@muc.de \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    /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).