New draft (#2) of SRFI 197: Expression Chaining Operators Arthur A. Gleckler (11 Jun 2020 05:43 UTC)
Re: New draft (#2) of SRFI 197: Expression Chaining Operators Marc Nieper-Wißkirchen (11 Jun 2020 09:57 UTC)
Re: New draft (#2) of SRFI 197: Expression Chaining Operators Marc Nieper-Wißkirchen (12 Jun 2020 08:29 UTC)
Re: New draft (#2) of SRFI 197: Expression Chaining Operators Arne Babenhauserheide (12 Jun 2020 12:28 UTC)
Re: New draft (#2) of SRFI 197: Expression Chaining Operators Marc Nieper-Wißkirchen (15 Jun 2020 09:47 UTC)
Re: New draft (#2) of SRFI 197: Expression Chaining Operators Marc Nieper-Wißkirchen (15 Jun 2020 10:56 UTC)
Re: New draft (#2) of SRFI 197: Expression Chaining Operators Marc Nieper-Wißkirchen (17 Jun 2020 07:53 UTC)
Re: New draft (#2) of SRFI 197: Expression Chaining Operators Arne Babenhauserheide (18 Jun 2020 14:04 UTC)

Re: New draft (#2) of SRFI 197: Expression Chaining Operators Marc Nieper-Wißkirchen 15 Jun 2020 09:47 UTC

Am Fr., 12. Juni 2020 um 03:14 Uhr schrieb Adam Nelson <xxxxxx@nels.onl>:

> (2) The library should export "<>" and "<...>" bound to the same
> values an implementation of SRFI 26 would bind them to. (See my
> comment in the section "Auxiliary syntax" here:
> https://srfi.schemers.org/srfi-148/srfi-148.html.)
>
> I can add that. That will also remove the need for the <...> branches of chain-and and chain-when that end in syntax-errors.

So the request is to drop "<...>" altogether (it should also be
dropped in a future SRFI 26') and replace it by "<> ...", which needs
fewer auxiliary syntax to be defined ("..." is already part of the
base), looks much nicer and conveys the meaning better.