Re: if-let/if-let*/and-let/..

[Eli Zaretskii]

> From: Michael Heerdegen <address@hidden>
> Cc: address@hidden,  address@hidden
> Date: Fri, 09 Mar 2018 16:16:14 +0100
> 
> The downside of only de-obsoleting now is that in the subsequent
> release, we would have to change the newly introduced foo-let* in a
> backward-incompatible way for the single-binding-tuple special case.
> 
> This backward-incompatible change is necessary to make foo-let* aliases
> of foo-let, which is our goal - foo-let has to support the
> single-binding-tuple syntax because it supported it all the time.

That foo-let did support that case doesn't necessarily mean it has to
support that in the future, nor that we must make that
backward-incompatible immediately.  We could simply let foo-let be as
it is today on the release branch and collect more experience before
we make our decision.  Does that make sense?