From: "Alfred M. Szmidt" <ams@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: philipk@posteo.net, arthur.miller@live.com, emacs-devel@gnu.org
Subject: Re: [External] : Re: cond* vs pcase
Date: Tue, 06 Feb 2024 12:41:44 -0500 [thread overview]
Message-ID: <E1rXPS4-0003ZC-3z@fencepost.gnu.org> (raw)
In-Reply-To: <SJ0PR10MB548817CF1242E8DB20D3675AF3462@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Tue, 6 Feb 2024 17:29:07 +0000)
The reason why we use COND, CASE, .. ASSQ, ASSOC, ASSOC-STRING .. EQ, EQL,
=, STRING= is about _intent_, and communicating with the user.
E.g, CL-CASE is _infinitly_ easier to understand (basically COND with
implicit EQL) than a generalized "COND". That is not to say that a
"generalized" COND, or a COND that works over "patterns" (which is not
over types!) is not useful, they like many things have their place.
But they should be used when they make _sense_.
(pcase escape
(?% (insert "%"))
(?h (insert host))
(?n (insert (or port "")))
(?u (insert (or user "")))
(?p (insert (or pass "")))
(?f (insert (or file "/"))))))
The change was literally case -> pcase .. that does not make sense.
next prev parent reply other threads:[~2024-02-06 17:41 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
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 [this message]
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
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=E1rXPS4-0003ZC-3z@fencepost.gnu.org \
--to=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 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).