News for hackers. Stuff that matters.
Re:What’s in a Continuation (2016) by yorwba on Sunday July 02, 2017 @04:20AM (#14681490)
From the description in th article, it seems like the content of the stack frame is usually not saved, which would break a lot of code that modifies a variable on the stack. E.g. if you are incrementing a counter in a loop and save a continuation into the middle of the loop, then on each invocation of that same continuation, the loop counter might have different values.

The obvious fix would be to never modify the content of a stack frame, instead recreating it with a different value for each iteration, but that doesn't strike me as very efficient.

Re:What’s in a Continuation (2016) by sillysaurus3 on Sunday July 02, 2017 @10:58AM (#14682749)
All local variables are saved by a continuation. EDIT: Nope.
Re:What’s in a Continuation (2016) by kazinator on Sunday July 02, 2017 @11:00AM (#14682765)
This can be easily demonstrated false in Scheme. Two continuations which capture the same environment can mutate it and see each other's mutations.

A continuation captures variable bindings similarly to a closure. (It just captures more than just variable bindings and more than just the lexically apparent ones.)

Re:What’s in a Continuation (2016) by sillysaurus3 on Sunday July 02, 2017 @12:48PM (#14683224)
Whoops. You're right, thank you.