Fwd: Video on continuations, and call/cc-safe programming in the SRFI
Bradley Lucier 22 Sep 2022 15:45 UTC
Forgot to CC the list.
-------- Forwarded Message --------
Subject: Re: Video on continuations, and call/cc-safe programming in the
SRFI
Date: Wed, 21 Sep 2022 12:13:30 -0400
From: Bradley Lucier <xxxxxx@math.purdue.edu>
To: Marc Nieper-Wißkirchen <xxxxxx@gmail.com>
CC: xxxxxx@purdue.edu
On 9/21/22 5:16 AM, Marc Nieper-Wißkirchen wrote:
>
> Am Di., 20. Sept. 2022 um 08:33 Uhr schrieb Marc Nieper-Wißkirchen
> <xxxxxx@gmail.com <mailto:xxxxxx@gmail.com>>:
>
> Am Di., 20. Sept. 2022 um 02:43 Uhr schrieb Bradley Lucier
> <xxxxxx@math.purdue.edu <mailto:xxxxxx@math.purdue.edu>>:
>
> In fact, `array-copy` seems easy to specify correctly without any
> new language but it is not clear what the specification of
> `array-copy!` should be. At the moment, it is the same as
> `array-copy` but this is obviously not intended.
>
> I will think about a way how to specify the "!" versions.
>
>
> Okay, I think I have a solution. Once the non-"!" versions are
> specified properly (using `array->list`, etc.), the "!" versions can be
> defined with precisely the same semantics but with the following
> addition: "It is an error if the continuation of each call to the
> array's getter is invoked more than once." (See the specification of
> `letrec` in R6RS and R7RS where this language comes from.)
>
> When this is done, the comment about "call/cc-safety" can be left in the
> non-normative section but the term isn't needed for the actual
> specification anymore.
>
> Marc
>
(CC'ing the list.)
With this commit:
https://github.com/gambiteer/srfi-231/commit/7ecfd3c26cd596a40ccbe196478fcc06bf9c2cb5
I've added a sentence along these lines to the Notes:
https://htmlpreview.github.io/?https://github.com/gambiteer/srfi-231/blob/call/cc-fix/srfi-231.html#Notes
With this change, I'm ready to ask Arthur to review this SRFI for
finalization.
Brad