From: Michael Heerdegen <michael_heerdegen@web.de>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: 60758-done@debbugs.gnu.org, 60758@debbugs.gnu.org,
Sean Whitton <spwhitton@spwhitton.name>
Subject: bug#60758: 29.0.60; while-let uses if-let* convention in contradiction to the docstring
Date: Sat, 14 Jan 2023 16:31:03 +0100 [thread overview]
Message-ID: <87y1q5rv48.fsf@web.de> (raw)
In-Reply-To: <c1bff04e-712a-2300-6633-3ea27c0ac8cd@daniel-mendler.de> (Daniel Mendler's message of "Fri, 13 Jan 2023 06:36:14 +0100")
Daniel Mendler <mail@daniel-mendler.de> writes:
> On 1/13/23 01:37, Sean Whitton wrote:
> > I agree that if-let is right, for these reasons. Now fixed, thank
> > you.
The special case of a SPEC of the form (SYMBOL SOMETHING) is supported
only for backward compatibility by `if-let'. We wanted to get rid of
this special syntax anomaly.
So it makes no sense to add this syntax to newly introduced macros. We
should fix the docstring of `while-let' instead - unless the goal of
getting rid of this syntax has changed. But then we should have a
discussion first. Instead it seems you just reverted a change by Lars
that was the result of a discussion in emacs-dev.
Michael.
next prev parent reply other threads:[~2023-01-14 15:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 19:21 bug#60758: 29.0.60; while-let uses if-let* convention in contradiction to the docstring Daniel Mendler
2023-01-13 0:37 ` Sean Whitton
2023-01-13 5:36 ` Daniel Mendler
2023-01-14 15:31 ` Michael Heerdegen [this message]
2023-01-14 15:35 ` Daniel Mendler
2023-01-14 16:11 ` Michael Heerdegen
2023-01-14 16:29 ` Daniel Mendler
2023-01-14 16:25 ` Sean Whitton
2023-01-14 16:35 ` Eli Zaretskii
2023-01-14 21:13 ` Sean Whitton
2023-01-14 22:13 ` Michael Heerdegen
2023-01-15 7:38 ` Eli Zaretskii
2023-01-15 17:02 ` Sean Whitton
2023-01-16 17:55 ` Michael Heerdegen
2023-01-16 20:36 ` Sean Whitton
2023-01-17 12:46 ` Michael Heerdegen
2023-01-14 16:58 ` Michael Heerdegen
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=87y1q5rv48.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=60758-done@debbugs.gnu.org \
--cc=60758@debbugs.gnu.org \
--cc=mail@daniel-mendler.de \
--cc=spwhitton@spwhitton.name \
/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.