From: Adam Porter <adam@alphapapa.net>
To: drew.adams@oracle.com
Cc: ams@gnu.org, arthur.miller@live.com, emacs-devel@gnu.org,
philipk@posteo.net
Subject: RE: [External] : Re: cond* vs pcase
Date: Tue, 6 Feb 2024 14:08:59 -0600 [thread overview]
Message-ID: <822c332c-1a85-4454-8978-0b1491981058@alphapapa.net> (raw)
In-Reply-To: <SJ0PR10MB5488FBA45DA4AC634791B577F3462@SJ0PR10MB5488.namprd10.prod.outlook.com>
> It says, in effect, "This just tests the
> value for simple equality (using this or
> that equality predicate)." It speaks
> quietly, humbly, clearly. >
> `pcase' advertises instead: "Here come the
> Big Guns, which can wrestle _anything_ to
> the ground! Stand in awe and wonder."
CL-CASE and PCASE neither say nor advertise anything. They have no
personal qualities. They are macros, not people.
(pcase foo
('bar (do-some-bar-stuff))
('baz (do-some-baz-fluff)))
is not more awful or wonderful than:
(cl-case foo
(bar (do-some-bar-stuff))
(baz (do-some-baz-fluff)))
And neither of them is worse than what they expand to:
(cond ((eql foo 'bar)
(do-some-bar-stuff))
((eql foo 'baz)
(do-some-baz-fluff)))
Nor is this:
(pcase foo
(1 'ONE)
(2 'TWO)
((cl-type function) (funcall foo))
(_ 'SOMETHING-ELSE))
any worse than what it expands to:
(cond ((eql foo 1)
'ONE)
((eql foo 2)
'TWO)
((cl-typep foo 'function)
(funcall foo))
(t
'SOMETHING-ELSE))
That example is not even a case of pattern-matching, as no patterns are
involved.
But if one needed to add a pattern, as in the common case of a
customization option having various possible value types, one may easily
do so, as in:
(pcase foo
(1 'ONE)
(2 'TWO)
((cl-type function) (funcall foo))
(`(,fn . ,arg) (funcall fn arg))
(_ 'SOMETHING-ELSE))
I cannot fathom how this optionally available "power" is a problem which
should consign PCASE to only exceptional cases, any more than Lisp's
power should consign it to only a few libraries, leaving the rest to be
implemented in lower-level languages; or any more than Emacs's power
should consign it to only a few use cases, leaving the the rest to be
implemented in utilities to be piped together in a shell.
next prev parent reply other threads:[~2024-02-06 20:08 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 14:30 cond* vs pcase Arthur Miller
2024-02-05 15:13 ` Eli Zaretskii
2024-02-05 16:06 ` Alfred M. Szmidt
2024-02-05 18:39 ` Philip Kaludercic
2024-02-06 12:30 ` Arthur Miller
2024-02-06 16:17 ` Alfred M. Szmidt
2024-02-06 16:35 ` [External] : " Drew Adams
2024-02-06 16:50 ` Philip Kaludercic
2024-02-06 17:27 ` Alfred M. Szmidt
2024-02-06 18:57 ` Philip Kaludercic
2024-02-06 19:04 ` Alfred M. Szmidt
2024-02-06 19:39 ` Philip Kaludercic
2024-02-06 23:17 ` [External] : " Drew Adams
2024-02-06 19:12 ` Drew Adams
2024-02-06 20:08 ` Adam Porter [this message]
2024-02-06 23:32 ` Drew Adams
2024-02-07 13:14 ` Arthur Miller
2024-02-07 13:43 ` Po Lu
2024-02-07 17:09 ` Drew Adams
2024-02-07 17:44 ` Tomas Hlavaty
2024-02-09 3:52 ` Richard Stallman
2024-02-07 18:00 ` Arthur Miller
2024-02-07 18:22 ` Alfred M. Szmidt
2024-02-08 1:55 ` Po Lu
2024-02-08 2:49 ` Philip Kaludercic
2024-02-08 3:36 ` Po Lu
2024-02-08 7:04 ` Eli Zaretskii
2024-02-08 17:01 ` Alfred M. Szmidt
2024-02-08 17:01 ` Alfred M. Szmidt
2024-02-09 1:30 ` Po Lu
2024-02-08 5:01 ` Po Lu
[not found] ` <DU2PR02MB10109B7AC39F995BFE266EF5396442@DU2PR02MB10109.eurprd02.prod.outlook.com>
2024-02-08 7:36 ` Sv: " Arthur Miller
2024-02-12 21:39 ` Stefan Monnier via Emacs development discussions.
2024-02-07 17:14 ` Drew Adams
2024-02-07 5:32 ` Yuri Khan
2024-02-07 12:43 ` Arthur Miller
2024-02-07 17:41 ` Alfred M. Szmidt
2024-02-07 18:36 ` Arthur Miller
2024-02-07 19:12 ` Alfred M. Szmidt
2024-02-07 21:20 ` Arthur Miller
2024-02-06 17:29 ` [External] : " Drew Adams
2024-02-06 17:41 ` Alfred M. Szmidt
2024-02-06 17:50 ` Thierry Volpiatto
2024-02-06 19:04 ` Alfred M. Szmidt
2024-02-07 15:03 ` Barry Fishman
2024-02-07 17:22 ` [External] : " Drew Adams
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=822c332c-1a85-4454-8978-0b1491981058@alphapapa.net \
--to=adam@alphapapa.net \
--cc=ams@gnu.org \
--cc=arthur.miller@live.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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.