| … | |
… | |
| 4 | TODO: more effective stack sharing by having one "default stack" for "simple" coroutines? |
4 | TODO: more effective stack sharing by having one "default stack" for "simple" coroutines? |
| 5 | TODO: verify exception frame changes and force stack copies? |
5 | TODO: verify exception frame changes and force stack copies? |
| 6 | |
6 | |
| 7 | - reimplement a new stack sharing algorithm. |
7 | - reimplement a new stack sharing algorithm. |
| 8 | - make stack sharing mandatory (it no longer uses a heuristic). |
8 | - make stack sharing mandatory (it no longer uses a heuristic). |
|
|
9 | - eval/die no longer cause weird problems under heavy use. |
| 9 | - Coro::Event could cause livelocks if it was used but |
10 | - Coro::Event could cause livelocks if it was used but |
| 10 | Event watchers were used directly. |
11 | Event watchers were used directly. |
| 11 | - Coro::Event should be cleaner and more efficient now. |
12 | - Coro::Event should be cleaner and more efficient now. |
| 12 | - minor incompatibility: subclassing is supported directly now |
13 | - minor incompatibility: subclassing is supported directly now |
| 13 | without going through a _coro_state member. |
14 | without going through a _coro_state member. |
