From: Richard Stallman <rms@gnu.org>
To: Psionic K <psionik@positron.solutions>
Cc: emacs-devel@gnu.org
Subject: Re: cond* Examples
Date: Wed, 08 Jan 2025 22:51:19 -0500 [thread overview]
Message-ID: <E1tVjZn-0002HB-RS@fencepost.gnu.org> (raw)
In-Reply-To: <CADQMGASN_MGmW0E6d8uAf_SczGaosM803vwACYQ9fD70pxBTHg@mail.gmail.com> (message from Psionic K on Mon, 6 Jan 2025 23:55:09 +0900)
[[[ 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. ]]]
Thanks for your comments.
> This feels inconsistent with `when-let*' and `if-let*' behavior, where
> there's an intuitive reason that every bind must succeed for the first
> or all body forms to evaluate. Is this a first-pass tradeoff?
What does "first-pass tradeoff" mean?
I never considered the possibility of checking each of the binding values.
That would be convenient when you want to test them all.
It would ne a nuisance when there is a variable that could be nil
and you don't want to test it.
I don't have strong feelings about this. Anyone who has an opinion
about this, please post it.
Regarding the general comments about other languages, I am indeed
trying to find a more elegant way to address the same issue that pcase
addresses. But doing this in Lisp is constrained by the
characteristic of Lisp that is its strongest feature: that code is
data built out of simple general-purpose data structures. This is the
furtherst step in that dieection that I saw a way to realize.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2025-01-09 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 14:55 cond* Examples Psionic K
2025-01-09 3:51 ` Richard Stallman [this message]
2025-01-09 13:35 ` Trevor Arjeski
2025-01-10 3:24 ` Richard Stallman
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=E1tVjZn-0002HB-RS@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=psionik@positron.solutions \
/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).