From: Daniel Mendler <mail@daniel-mendler.de>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Sean Whitton <spwhitton@spwhitton.name>,
60758@debbugs.gnu.org, 60758-done@debbugs.gnu.org
Subject: bug#60758: 29.0.60; while-let uses if-let* convention in contradiction to the docstring
Date: Sat, 14 Jan 2023 17:29:19 +0100 [thread overview]
Message-ID: <d7e6d332-332e-ece0-31f9-1f52da0bcbcb@daniel-mendler.de> (raw)
In-Reply-To: <87o7r1p03t.fsf@web.de>
On 1/14/23 17:11, Michael Heerdegen wrote:
> Daniel Mendler <mail@daniel-mendler.de> writes:
>
>> But then it may make sense to deprecate `if-let` and `when-let`
>> altogether in favor of `if-let*` and `when-let*`?
>
> I don't recall why that hasn't been done. There was a very long
> discussion about it. Probably the answer was "the syntax had been there
> for too long and now too many packages use it and we don't want to break
> them", I don't recall. Maybe you can find these discussions. There had
> not been an agreement at least.
Okay, I see. Would it be possible to deprecate the single-binding syntax
via `macroexp-warn-and-return'? Or do you plan to introduce byte
compiler warnings? Given that `while-let' has been introduced without
support for single bindings it may be better then to deprecate the
starred variants in the long term, such that we end up only with
`if-let', `when-let', `while-let' etc.?
Daniel
next prev parent reply other threads:[~2023-01-14 16:29 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
2023-01-14 15:35 ` Daniel Mendler
2023-01-14 16:11 ` Michael Heerdegen
2023-01-14 16:29 ` Daniel Mendler [this message]
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=d7e6d332-332e-ece0-31f9-1f52da0bcbcb@daniel-mendler.de \
--to=mail@daniel-mendler.de \
--cc=60758-done@debbugs.gnu.org \
--cc=60758@debbugs.gnu.org \
--cc=michael_heerdegen@web.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.