diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2017-08-30 21:32:54 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2017-08-30 21:32:54 -0700 |
commit | 53930831c4185c5ccb56864c881acf6d67dd1bd1 (patch) | |
tree | 8826f80e35f7e168a1554176ad4108dca1c0fa42 /045closure_name.cc | |
parent | b74744cd5851e034a88d4a335b22a372ebb39237 (diff) | |
download | mu-53930831c4185c5ccb56864c881acf6d67dd1bd1.tar.gz |
3986 - bring back delimited continuations
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.
Diffstat (limited to '045closure_name.cc')
0 files changed, 0 insertions, 0 deletions