From: Richard Stallman <rms@gnu.org>
To: emacs-devel@gnu.org
Subject: Using "pcase" as part of names is inhelpful.
Date: Sat, 09 Dec 2017 17:00:58 -0500 [thread overview]
Message-ID: <E1eNnB4-0005Sd-2f@fencepost.gnu.org> (raw)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
The construct 'pcase' uses patterns to test and destructure
objects while selecting among various cases.
Now we are adding other constructs that use patterns to destructure
objects. These constructs have nothing to do with selecting among
cases. Thus, 'pcase' in their names makes for misleading names.
The only part of the name 'pcase' that refers to the use of
patterns is the letter 'p'.
Referring users to 'pcase' to understand the use of patterns is
unhelpful since 'pcase' includes conceptual complexity (about cases)
that isn't present in the new constructs.
We should give the new constructs names that fit them without a
distracting element. What would be good new names?
We could use 'plet' and 'plambda'. Or 'pattern-let' and 'pattern-lambda'.
We could follow the example of Common Lisp 'destructuring-bind', to
create 'destructuring-let' and 'destructuring-lambda'.
Let's mark the old names 'pcase-...' obsolete so that they won't build
up in Lisp code.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.
next reply other threads:[~2017-12-09 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 22:00 Richard Stallman [this message]
2017-12-09 22:35 ` Using "pcase" as part of names is inhelpful John Wiegley
2017-12-09 23:01 ` Paul Eggert
2017-12-10 21:44 ` Richard Stallman
2017-12-10 1:07 ` Robert Weiner
2017-12-10 21:45 ` Richard Stallman
2017-12-11 14:31 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1eNnB4-0005Sd-2f@fencepost.gnu.org \
--to=rms@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 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.