Message245300
Regarding the idea of doing a typedef for the new coro type at the C level: looking further at the way the new type integrates with the eval loop, it's essential that they actually retain the exact same memory layout if we don't want to rewrite a whole lot of code.
I still like the idea of adding the typedef so we can at least make the distinction in cases where the C level handling *isn't* shared between the two types, it would just need a great big disclaimer saying that the memory layout of the coroutine struct can't be altered independently of the generator layout. |
|
Date |
User |
Action |
Args |
2015-06-13 07:16:38 | ncoghlan | set | recipients:
+ ncoghlan, gvanrossum, scoder, vstinner, asvetlov, Yury.Selivanov, Ben.Darnell, yselivanov |
2015-06-13 07:16:38 | ncoghlan | set | messageid: <1434179798.36.0.44641926346.issue24400@psf.upfronthosting.co.za> |
2015-06-13 07:16:38 | ncoghlan | link | issue24400 messages |
2015-06-13 07:16:37 | ncoghlan | create | |
|