… | |
… | |
8 | - INCOMPATIBLE CHANGE: unreferenced coro objects will now be |
8 | - INCOMPATIBLE CHANGE: unreferenced coro objects will now be |
9 | destroyed and cleaned up automatically (e.g. async { schedule }). |
9 | destroyed and cleaned up automatically (e.g. async { schedule }). |
10 | - Coro::State->is_destroyed is now called is_zombie. |
10 | - Coro::State->is_destroyed is now called is_zombie. |
11 | - implement a Coro->safe_cancel method that might fail, but |
11 | - implement a Coro->safe_cancel method that might fail, but |
12 | cancels in a "safer" way if it succeeds. |
12 | cancels in a "safer" way if it succeeds. |
|
|
13 | - get rid of two hash-accesses when initialising a new Coro - this |
|
|
14 | speeds up coro creation by almost a factor of two. |
13 | - croak when a coro that is being cancelled tries to block |
15 | - croak when a coro that is being cancelled tries to block |
14 | (e.g. while executing a guard block), instead of crashing or |
16 | (e.g. while executing a guard block), instead of crashing or |
15 | deadlocking. |
17 | deadlocking. |
16 | - use a more robust and also faster method to identify Coro::State |
18 | - use a more robust and also faster method to identify Coro::State |
17 | objects - speeds up everything a bit. |
19 | objects - speeds up everything a bit. |
… | |
… | |
27 | callbacks (best effort). |
29 | callbacks (best effort). |
28 | - move on_destroy into the slf_frame, to allow extension slf |
30 | - move on_destroy into the slf_frame, to allow extension slf |
29 | functions to have destructors. |
31 | functions to have destructors. |
30 | - get rid if coro refcounting - simply crash in other interpreter |
32 | - get rid if coro refcounting - simply crash in other interpreter |
31 | threads by nulling the pointers on clone. |
33 | threads by nulling the pointers on clone. |
|
|
34 | - simplify warn/die hook handling when loading Coro - the convoluted |
|
|
35 | logic seems to be no longer neccessary. |
32 | |
36 | |
33 | 5.372 Wed Feb 23 06:14:30 CET 2011 |
37 | 5.372 Wed Feb 23 06:14:30 CET 2011 |
34 | - apparently mingw doesn't provide a working gettimeofday, try to |
38 | - apparently mingw doesn't provide a working gettimeofday, try to |
35 | work around that by relying on Time::HiRes (indirectly brought to |
39 | work around that by relying on Time::HiRes (indirectly brought to |
36 | my attention by Max Maischein). |
40 | my attention by Max Maischein). |