Email list hosting service & mailing list manager

Draft #11 deadline for feedback Wolfgang Corcoran-Mathe (20 Jun 2021 16:31 UTC)
Re: Draft #11 deadline for feedback Marc Nieper-Wißkirchen (20 Jun 2021 16:40 UTC)
Re: Draft #11 deadline for feedback Wolfgang Corcoran-Mathe (20 Jun 2021 16:53 UTC)
Re: Draft #11 deadline for feedback Marc Nieper-Wißkirchen (20 Jun 2021 17:43 UTC)
Re: Draft #11 deadline for feedback Marc Nieper-Wißkirchen (20 Jun 2021 18:23 UTC)
Re: Draft #11 deadline for feedback Wolfgang Corcoran-Mathe (20 Jun 2021 18:42 UTC)
Re: Draft #11 deadline for feedback Marc Nieper-Wißkirchen (20 Jun 2021 18:47 UTC)
Re: Draft #11 deadline for feedback Wolfgang Corcoran-Mathe (20 Jun 2021 18:53 UTC)
Re: Draft #11 deadline for feedback Marc Nieper-Wißkirchen (20 Jun 2021 18:59 UTC)
Re: Draft #11 deadline for feedback Wolfgang Corcoran-Mathe (20 Jun 2021 19:13 UTC)
Re: Draft #11 deadline for feedback John Cowan (26 Jun 2021 11:18 UTC)
Re: Draft #11 deadline for feedback Marc Nieper-Wißkirchen (26 Jun 2021 11:46 UTC)
Re: Draft #11 deadline for feedback Wolfgang Corcoran-Mathe (26 Jun 2021 16:46 UTC)
Re: Draft #11 deadline for feedback Marc Nieper-Wißkirchen (26 Jun 2021 18:47 UTC)
Re: Draft #11 deadline for feedback Wolfgang Corcoran-Mathe (26 Jun 2021 21:11 UTC)
Re: Draft #11 deadline for feedback John Cowan (26 Jun 2021 19:35 UTC)
Re: Draft #11 deadline for feedback Marc Nieper-Wißkirchen (26 Jun 2021 21:57 UTC)

Re: Draft #11 deadline for feedback Wolfgang Corcoran-Mathe 20 Jun 2021 18:53 UTC

On 2021-06-20 20:47 +0200, Marc Nieper-Wißkirchen wrote:
> Am So., 20. Juni 2021 um 20:42 Uhr schrieb Wolfgang Corcoran-Mathe <
> xxxxxx@sigwinch.xyz>:
>
> > PPS Unrelated to this but related to my ongoing discussion with Shiro:
> > SRFI
> > > 224 is silent with respect to multiple returns from the higher-order
> > > procedures. Given that SRFI 224's objects are purely functional, the
> > purist
> > > approach of full compatibility with call/cc makes sense (and which we
> > also
> > > have with all R7RS base procedures).
> >
> > Agreed on approach, but what changes would you suggest to make this
> > clear?
> >
>
> One can use the language from R6RS/R7RS (see, for example, 'map' or
> 'vector-map'):
>
> "If multiple returns occur from xxx, the values returned by earlier returns
> are not mutated."

This is what I was assuming.  This is just boilerplate, though.
Would it be sufficient to add a "note on multiple returns" stating
this requirement for all higher-order functions in the SRFI?  There
are quite a few.

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

"Conquering the galaxy is what bacteria with spaceships would
do--knowing no better, having no choice." --Greg Egan, _Disapora_