From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Artur Malabarba <bruce.connor.am@gmail.com>, 20784@debbugs.gnu.org
Subject: bug#20784: 25.0.50; pcase documentation on t and nil
Date: Fri, 12 Jun 2015 19:31:10 +0200 [thread overview]
Message-ID: <87ioasdeap.fsf@web.de> (raw)
In-Reply-To: <jwva8w66xhp.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Thu, 11 Jun 2015 12:22:28 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> We currently don't have a special "fail" pattern which simply never
> matches. Of course, you can make one up (e.g. (guard nil)).
(or) would also do it, but raises (error "Please avoid it") (BTW
(or _) raises that error, too). Why are those (error "Please avoid it")
calls useful?
> I think making nil such a pattern would probably lead to more
> errors/confusion than anything, since it's extremely rare to need such
> a pattern.
Agreed.
> That's pretty much what SELFQUOTING is. IF you think renaming it to
> ATOM would help, then we could do that.
I would prefer that over SELFQUOTING because
SELFQUOTING is a shorthand for 'SELFQUOTING.
sounds like a tautology.
> As explained the use of `eq' is supposed to be a pure optimization with
> no semantics effect.
I see. Then I guess it would make sense to merge these two lines in the
` doc?
STRING matches if the object is ‘equal’ to STRING.
ATOM matches if the object is ‘eq’ to ATOM.
into
ATOM matches if the object is ‘equal’ to ATOM.
Regards,
Michael.
next prev parent reply other threads:[~2015-06-12 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 20:20 bug#20784: 25.0.50; pcase documentation on t and nil Artur Malabarba
2015-06-11 3:07 ` Stefan Monnier
2015-06-11 12:24 ` Artur Malabarba
2015-06-11 12:33 ` Michael Heerdegen
2015-06-11 15:23 ` Stefan Monnier
2015-06-11 13:18 ` Michael Heerdegen
2015-06-11 16:22 ` Stefan Monnier
2015-06-12 17:31 ` Michael Heerdegen [this message]
2015-06-16 16:43 ` Stefan Monnier
2015-06-11 16:34 ` Stefan Monnier
2015-06-12 17:36 ` Michael Heerdegen
2016-07-01 2:39 ` npostavs
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=87ioasdeap.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=20784@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
--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.