all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: jwiegley@gmail.com, emacs-devel@gnu.org
Subject: Re: pcase docs
Date: Sat, 23 Jan 2016 16:50:04 +0200	[thread overview]
Message-ID: <83y4bg4ag3.fsf@gnu.org> (raw)
In-Reply-To: <87vb6k8jfz.fsf@web.de> (message from Michael Heerdegen on Sat, 23 Jan 2016 15:22:08 +0100)

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: jwiegley@gmail.com,  emacs-devel@gnu.org
> Date: Sat, 23 Jan 2016 15:22:08 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > > Surely not!  I just had the time to read the code, carefully (I had to,
> > > to be able to write my el-search.el thing).  Most others don't care
> > > because they just don't care, I think.
> >
> > But this stuff is widely used, by several different individuals.  How
> > do they know what to put in the code, if they, like me, are confused
> > about the purpose and the usage?
> 
> Dunno.  If it helps: I had spent really a lot of time into understanding
> pcase.  More time than you can probably invest, doing all the work you
> do.  And I made lots of errors over weeks after had finally internalized
> everything.

So maybe we should drop everything and make sure those doc strings are
corrected?

> > > Actually `pcase-defmacro' is easy to understand if you understood
> > > `defmacro': You define a pattern by its name and by the arguments it
> > > will accept.
> >
> > But 'pcase' patterns don't accept any arguments, they are matched
> > against a value of an expression.  So how to understand "arguments" in
> > this context?
> 
> pcase-defmacro can only define patterns that are used like function
> calls, (pattern-name pattern-args), like
> 
>  
>   (pred fun)
>   (guard expr)
>   (or pattern...)
> 
> In the sense of pcase-defmacro, FUN, EXPR or the PATTERNs play the role
> of arguments of the pattern.

I don't think I see any of this in the doc string...

> > And how to explain that a pattern that starts with "`(list" will
> > somehow end up using the pattern defined with "(pcase-defmacro map"?
> 
> No, `map' doesn't define `, it defines a pattern named `map' (that
> currently is rarely used, or nowhere).

That's the problem: that the pattern 'map' is not used.  Instead, I
see its sub-classes being used as pcase patterns.

> (pcase-defmacro greater-than (number)
>   `(and (pred numberp)
>         (pred (lambda (x) (< ,number x)))))
> 
> Then any occurrence of (greater-than N) in any pcase pattern is simply
> substituted with
> 
>   (and (pred numberp)
>        (pred (lambda (x) (< N x))))
> 
> That's it.

That's what I expected to see when I saw this:

  (pcase-defmacro map (&rest args)

I expected to see its use like this:

  (map SOMETHING)

But instead I see this:

  (pcase type
    (`list (map-pairs map))
    (`hash-table (map--into-hash-table map))
    (_ (error "Not a map type name: %S" type))))

IOW, there's no 'map', which was defined with pcase-defmacro, but
there are 'list' and 'hash-table', which weren't.  And btw, why "`list"
instead of "`(list"?



  reply	other threads:[~2016-01-23 14:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 19:47 pcase docs Eli Zaretskii
2016-01-22 18:07 ` John Wiegley
2016-01-22 19:46   ` Michael Heerdegen
2016-01-22 19:58     ` Michael Heerdegen
2016-01-22 21:30       ` Eli Zaretskii
2016-01-23 10:16         ` Michael Heerdegen
2016-01-23 11:43           ` Eli Zaretskii
2016-01-23 12:05             ` Michael Heerdegen
2016-01-23 13:35               ` Eli Zaretskii
2016-01-23 14:22                 ` Michael Heerdegen
2016-01-23 14:50                   ` Eli Zaretskii [this message]
2016-01-23 15:18                     ` Michael Heerdegen
2016-01-24  8:50                       ` Nicolas Petton
2016-01-23 15:51                 ` Michael Heerdegen
2016-01-23 12:28             ` Alan Mackenzie
2016-01-23 13:13               ` Eli Zaretskii
2016-01-23 20:48               ` Drew Adams
2016-01-24  5:07             ` Stefan Monnier
2016-01-22 21:28     ` Eli Zaretskii

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=83y4bg4ag3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jwiegley@gmail.com \
    --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 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.