about summary refs log tree commit diff stats
path: root/076continuation.cc
Commit message (Collapse)AuthorAgeFilesLines
* 4113Kartik K. Agaram2017-11-051-0/+3
|
* 4108Kartik K. Agaram2017-11-051-1/+2
|
* 4107Kartik K. Agaram2017-11-051-0/+36
| | | | Return other values along with the current continuation.
* 4105Kartik K. Agaram2017-11-031-4/+4
|
* 4104Kartik K. Agaram2017-11-031-1/+1
| | | | | Stop hardcoding Max_depth everywhere; we had a default value for a reason but then we forgot all about it.
* 4103 - continuations no longer cause memory corruptionKartik K. Agaram2017-11-031-5/+100
|
* 3994Kartik K. Agaram2017-09-131-5/+5
|
* 3989Kartik K. Agaram2017-09-011-19/+19
|
* 3988Kartik K. Agaram2017-09-011-3/+6
|
* 3986 - bring back delimited continuationsKartik K. Agaram2017-08-301-0/+185
They're back after a long hiatus: commit 2295 in Oct 2015. I'm not convinced anymore that this is actually a correct implementation of continuations. Issues on at least two fronts: a) These aren't safe yet. Since continuations can be called multiple times, we need to disable reclamation of locals inside a continuation. There may be other type- or memory-safety issues. However, delimited continuations at least seem possible to make safe. Undelimited continuations (call/cc) though are permanently out. b) They may not actually be as powerful as delimited continuations. Let's see if I can build 'yield' out of these primitives.