all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>,
	Sean Whitton <spwhitton@spwhitton.name>
Cc: control@debbugs.gnu.org, 73853@debbugs.gnu.org,
	monnier@iro.umontreal.ca, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#73853: 31.0.50; Should and-let* become a synonym for when-let*?
Date: Sat, 26 Oct 2024 12:25:43 -0700	[thread overview]
Message-ID: <cce27780-e6f6-3a63-fcfe-b04f3cab633a@gmail.com> (raw)
In-Reply-To: <87a5ew5few.fsf@web.de>

On 10/22/2024 8:24 AM, Michael Heerdegen via Bug reports for GNU Emacs, 
the Swiss army knife of text editors wrote:
> Sean Whitton <spwhitton@spwhitton.name> writes:
> 
>> retitle 73853 Should and-let* become a synonym for when-let*?
>> thanks
> 
> Thanks for the fine summary.
> 
>>    - I'd like to go ahead and install a patch marking when-let and if-let
>>      as obsolete, unless Michael is keen to be the one to do it as the
>>      initiator of the previous effort
> 
> He is not, feel free to go ahead when there are no objections from
> others.

I missed this before this change merged, but I think I'd have preferred 
to keep 'if-let' and 'when-let' around, and only to obsolete their 
backward-compatible forms, with the goal of removing that 
backward-compatibility one day. Then we'd eventually result in 'if-let' 
and 'when-let' (with their preferred semantics) being the only forms around.

It's a minor thing, but I generally read a "*" suffix on a 
function/macro name to mean "this function is an extension or 
modification of the non-* form". But if there's no (non-obsolete) 
non-star form then that breaks down.

On the other hand, the way bindings work in 'if-let*' and 'when-let*' 
are closer to 'let*' than 'let'. I think that's a false friend though, 
since they're only similar, not actually the same (of course the 
semantics couldn't be exactly the same or there'd be no reason for 
'if-let*' and 'when-let*' to exist).

Maybe I'm the odd one out here and everyone else prefers to keep 
'if-let*' for the long term, in which case I won't dig my heels in on 
this issue.





  parent reply	other threads:[~2024-10-26 19:25 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17 16:27 bug#73853: 31.0.50; and-let* is useless Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-17 16:40 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-18  2:11 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-18 23:42   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-19  3:50     ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-21  7:07     ` Augusto Stoffel
2024-10-21  8:57       ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-21 12:09         ` Sean Whitton
2024-10-19  3:38   ` Sean Whitton
2024-10-20 12:24     ` Stefan Kangas
2024-10-22 14:47       ` bug#73853: 31.0.50; Should and-let* become a synonym for when-let*? Sean Whitton
2024-10-22 15:24         ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-23 14:05           ` Stefan Kangas
2024-10-24  8:51             ` Sean Whitton
2024-10-25 12:09               ` Sean Whitton
2024-10-30  9:42                 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-26 19:25           ` Jim Porter [this message]
2024-10-27  7:08             ` Stefan Kangas
2024-10-27  9:16               ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27 10:12                 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27 11:24                   ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27 11:32                     ` Sean Whitton
2024-10-27 11:44                     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27 12:28                       ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27 13:10                         ` Sean Whitton
2024-10-27 13:22                         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-28  9:39                           ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27 14:41                 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-28 13:58                   ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-28 14:32                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27 20:00                 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-28  2:15           ` Howard Melman
2024-10-28  3:19             ` Sean Whitton
2024-10-29 15:21 ` Jonas Bernoulli
2024-10-29 16:36   ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-30  0:49   ` Sean Whitton
2024-10-30 12:55   ` Corwin Brust

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=cce27780-e6f6-3a63-fcfe-b04f3cab633a@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=73853@debbugs.gnu.org \
    --cc=control@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=monnier@iro.umontreal.ca \
    --cc=spwhitton@spwhitton.name \
    --cc=stefankangas@gmail.com \
    /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.