From: "Alfred M. Szmidt" <ams@gnu.org>
To: arthur miller <arthur.miller@live.com>
Cc: emacs-devel@gnu.org
Subject: Re: Better documentation for non-binding clauses of if-let and friends
Date: Mon, 11 Nov 2024 04:58:23 -0500 [thread overview]
Message-ID: <E1tARBf-00019h-Sl@fencepost.gnu.org> (raw)
In-Reply-To: <DU2PR02MB10109FAD6856DDB956AA1904596582@DU2PR02MB10109.eurprd02.prod.outlook.com> (message from arthur miller on Mon, 11 Nov 2024 09:28:52 +0000)
That is the gotcha that got me: it says SPEC is "like let*", so this "-let*"
in the name take my mind to believe it established ordinary let*-bindings.
However, in while-let, these are not ordinary, but read-only. So they are
not the same, since they don't obey the ordinary behavior of let* bindings.
I agree, but the question really is what should be done -- either
satisfy one camp or the other.
I personally do not get what one gets from using WHILE-LET -- the
construct seems forced, and very rare to use.
IF-LET, WHEN-LET I can maybe guess but they too seem force constructs,
and why isn't there a UNLESS-LET and OR-LET*? But I'll leave it at
that, personal preferences and all.
> But I agree with you that the manual is incomplete or even
> wrong here.
If that semantic of while-let is desirable to have, than the manual would
have to catch the details of while-let and its non-general nature, read-only
semantic of bindings and perhaps mention the named-let as a more general
alternative.
Yup.
next prev parent reply other threads:[~2024-11-11 9:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 9:28 Better documentation for non-binding clauses of if-let and friends arthur miller
2024-11-11 9:58 ` Alfred M. Szmidt [this message]
2024-11-11 10:23 ` Sv: " arthur miller
2024-11-11 10:26 ` Joost Kremers
2024-11-11 10:53 ` Sv: " arthur miller
2024-11-11 11:18 ` Joost Kremers
2024-11-11 21:21 ` [External] : " Drew Adams
2024-11-11 22:51 ` Joost Kremers
2024-11-12 0:26 ` Drew Adams
2024-11-12 8:07 ` Joost Kremers
-- strict thread matches above, loose matches on Subject: below --
2024-11-08 16:25 Is this a bug in while-let or do I missunderstand it? arthur miller
2024-11-09 9:29 ` Yuri Khan
2024-11-09 13:03 ` Sv: " arthur miller
2024-11-09 13:15 ` Yuri Khan
2024-11-09 13:38 ` Sv: " arthur miller
2024-11-09 13:41 ` Yuri Khan
2024-11-09 13:47 ` Sv: " arthur miller
2024-11-09 14:04 ` Yuri Khan
2024-11-09 16:33 ` Alfred M. Szmidt
2024-11-09 16:44 ` Eli Zaretskii
2024-11-09 18:07 ` [External] : " Drew Adams
2024-11-09 18:18 ` Alfred M. Szmidt
2024-11-09 20:02 ` Jens Schmidt
2024-11-10 11:44 ` Alfred M. Szmidt
2024-11-10 12:24 ` Better documentation for non-binding clauses of if-let and friends Jens Schmidt
2024-11-10 14:51 ` Sean Whitton
2024-11-10 16:58 ` Jens Schmidt
2024-11-11 10:03 ` Alfred M. Szmidt
2024-11-11 8:20 ` Alfred M. Szmidt
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=E1tARBf-00019h-Sl@fencepost.gnu.org \
--to=ams@gnu.org \
--cc=arthur.miller@live.com \
--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).