From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] fix/bug-3133-pcase-doc 1181796 01/13: do ‘s/UPattern/U-pattern/g’, ‘s/QPattern/Q-pattern/g’
Date: Sun, 13 May 2018 19:46:17 +0200 [thread overview]
Message-ID: <874ljb78k6.fsf@gnuvola.org> (raw)
In-Reply-To: <jwv8t8oor63.fsf-monnier+emacsdiffs@gnu.org> (Stefan Monnier's message of "Sat, 12 May 2018 11:01:16 -0400")
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
() Stefan Monnier <monnier@IRO.UMontreal.CA>
() Sat, 12 May 2018 11:01:16 -0400
Hmm... I think this text should be changed to use the term
"pattern" for "U(-)pattern".
I've come around to this pov as well. See latest commits.
WRT Q-pattern:
My understanding is that `QPAT is an "extension" in deed (since
it's implemented via ‘pcase-defmacro’), but perhaps "innate" in
spirit. I moved the "structural pattern" stuff to the
(pcase-defmacro \` (qpat) ...)
docstring and added a comment in ‘pcase--make-docstring’ (but
have not changed any code). I think if we can get `QPAT to be
first in the extensions docs (in *Help*), this would satisfy
both the maintainability best practice (keep documentation near
its code) and the user experience best practice (good flow,
ordering).
What do people think?
--
Thien-Thi Nguyen -----------------------------------------------
(defun responsep (query)
(pcase (context query)
(`(technical ,ml) (correctp ml))
...)) 748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2018-05-13 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180511165048.32157.10695@vcs0.savannah.gnu.org>
[not found] ` <20180511165051.022C820545@vcs0.savannah.gnu.org>
2018-05-12 15:01 ` [Emacs-diffs] fix/bug-3133-pcase-doc 1181796 01/13: do ‘s/UPattern/U-pattern/g’, ‘s/QPattern/Q-pattern/g’ Stefan Monnier
2018-05-13 17:46 ` Thien-Thi Nguyen [this message]
2018-05-15 15:40 ` Michael Heerdegen
2018-05-15 18:29 ` Stefan Monnier
2018-05-16 19:17 ` Thien-Thi Nguyen
2018-05-18 12:51 ` Stefan Monnier
2018-05-18 16:16 ` Thien-Thi Nguyen
2018-05-18 22:13 ` 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=874ljb78k6.fsf@gnuvola.org \
--to=ttn@gnu.org \
--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).