Hi Marc and the SRFI 248 list,

Thanks for your work on this SRFI! A few comments:

The abstract is opaque. Many readers will probably give up after
trying to parse the first sentence. Please make it clearer.

The Rationale claims that "it has become increasingly clear that
[undelimited continuations] do not provide the right abstraction".
Citation needed! Please link to someone making this argument, or
make it yourself.

At the end of the Rationale you write "If it were not for call/cc,
the system could dispense with dynamic-wind." This is cryptic, and
is not elucidated anywhere in the SRFI. In any case, what's it
doing in the Rationale?

Please explain what the examples do and how they work.
make-coroutine-generator is at least described in SRFI 158, but
for-each->fold is novel. It's not obvious what it means
to "transform a procedure with for-each-like semantics describing
an abstract list into a procedure with fold-like semantics
describing the same abstract list."

What does "the dynamic extent (as determined by dynamic-wind)"
mean? Is the intended meaning "the dynamic extent (as defined in
[the RnRS section describing dynamic-wind])"?

Please simplify this: "The implementation must check the
restrictions on 'handler' to the extent performed by applying it
as described when it is called as a result of a call to 'raise' or
'raise-continuable'."

Please indent 'guard'. Use literal <br />s and no-break spaces
if there's really no other way.

guard: "It then binds the raised exception ..." For "exception"
read "object", I think.

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