From: Noam Postavsky <npostavs@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: pcase: Semantics of atom QPATS
Date: Sat, 16 Jun 2018 09:42:40 -0400 [thread overview]
Message-ID: <CAM-tV-_-wzTgFzJtk+Bnf+_cSvfQnuD_6WLrQT+rwqapu2R8gQ@mail.gmail.com> (raw)
In-Reply-To: <87zhzvtced.fsf@web.de>
On 16 June 2018 at 03:32, Michael Heerdegen <michael_heerdegen@web.de> wrote:
>> > - ((or (stringp qpat) (integerp qpat) (symbolp qpat)) `',qpat)
>> > + ((or (stringp qpat) (numberp qpat) (symbolp qpat)) `',qpat)
>>
>> Any reasons to use numberp and not number-or-marker-p?
>
> Is it likely that someone constructs a pcase pattern with a literal
> marker in it? Note this is about the pattern, not about the matched
> value.
It would be pretty difficult to do that since markers don't have a
read syntax. It's possible using a macro which expands to a pcase
form, if you can handle the nested backquotes...
next prev parent reply other threads:[~2018-06-16 13:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 0:40 pcase: Semantics of atom QPATS Michael Heerdegen
2018-06-11 14:09 ` Stefan Monnier
2018-06-11 14:45 ` Drew Adams
2018-06-11 15:24 ` Stefan Monnier
2018-06-11 20:53 ` Michael Heerdegen
2018-06-13 3:41 ` Michael Heerdegen
2018-06-13 12:52 ` Stefan Monnier
2018-06-16 4:03 ` Michael Heerdegen
2018-06-16 6:57 ` Eli Zaretskii
2018-06-16 7:32 ` Michael Heerdegen
2018-06-16 7:49 ` Eli Zaretskii
2018-06-17 13:35 ` Michael Heerdegen
2018-06-16 13:42 ` Noam Postavsky [this message]
2018-06-16 12:57 ` 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=CAM-tV-_-wzTgFzJtk+Bnf+_cSvfQnuD_6WLrQT+rwqapu2R8gQ@mail.gmail.com \
--to=npostavs@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
--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 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).