This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients Ben.Darnell, Yury.Selivanov, asvetlov, gvanrossum, ncoghlan, scoder, vstinner, yselivanov
Date 2015-06-13.07:16:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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:38ncoghlansetrecipients: + ncoghlan, gvanrossum, scoder, vstinner, asvetlov, Yury.Selivanov, Ben.Darnell, yselivanov
2015-06-13 07:16:38ncoghlansetmessageid: <>
2015-06-13 07:16:38ncoghlanlinkissue24400 messages
2015-06-13 07:16:37ncoghlancreate