New to R5RS, do we reaffirm the sometimes debated dynamic-wind?
Not in Schemes which provide threads.
Threading requires primitives beyond the scope of WG1. QED.
First of all, nothing is beyond the scope of WG1 unless WG1 declares it so, which has not happened.
Second, not standardizing threads is not equivalent to standardizing the absence of threads. All major Scheme implementations have threads, and that can't just be ignored.
Finally, the fact that a procedure can be implemented in terms of existing procedures has never been a bar to standardizing it. As obvious examples, consider ABS, GCD, LCM, INTEGER?, ZERO? and friends, MAX, MIN, NUMBER->STRING, STRING->NUMBER, LIST, LENGTH, APPEND, REVERSE, LIST-TAIL, ASSOC and friends, MEMBER and friends, CHAR=? and friends, STRING, STRING-APPEND, STRING->LIST, LIST->STRING, VECTOR, MAP, FOR-EACH, EVAL, WITH-*-*-FILE, WRITE, DISPLAY, NEWLINE/.
Replying to [comment:4 cowan]:
First of all, nothing is beyond the scope of WG1 unless WG1 declares it so, which has not happened. Second, not standardizing threads is not equivalent to standardizing the absence of threads. All major Scheme implementations have threads, and that can't just be ignored. Finally, the fact that a procedure can be implemented in terms of existing procedures has never been a bar to standardizing it.
If you have only winding continuations you have no other options. If you have classic call-with-current-continuation, you can have both. Additionally, the case of dynamic-wind however, is a fairly clear case of moving in exactly the opposite direction of the Prime Clingerism. WG2 is far less constrained in those terms.
The WG voted to reaffirm R5RS dynamic-wind as part of the core.
No. dynamic-wind is properly the realm of WG2 as it is directly implementable on top of the R4RS non-winding call-with-current-continuation.