Re: either-guard reference implementation Wolfgang Corcoran-Mathe 17 Jul 2020 13:40 UTC

On 2020-07-17 07:55 +0200, Marc Nieper-Wißkirchen wrote:
> I think it would have made very much sense to keep compatibility with
> SRFI 2 and vote for reverting this change. The allowance of an empty
> body doesn't cost anything and is actually what makes "and-let*" (and
> "either-let*") a generalization of "and".

The "change" was actually made a while ago, in 851ae058 (2020-07-03);
my pull request yesterday was just a patch to bring the implementation
into line with what the spec says.  It's unfortunate that we didn't
get a chance to debate this change in semantics at the time.  However,
I think that changing the SRFI to make maybe-let*, etc. compatible
with SRFI 2 again would be too much of a change at this late date.

I don't particularly like the empty-body forms of and-let*, and I'm
happy with how much simpler maybe-let* and friends are now with
those forms eliminated.

Regards,

--
Wolfgang Corcoran-Mathe  <xxxxxx@sigwinch.xyz>

"Scientists must be optimists at heart, in order to block out the
incessant chorus of those who say 'It cannot be done.'"
--Academician Prokhor Zakharov