Author ncoghlan
Recipients Mark.Shannon, deleted0524, erik.bray, gregory.p.smith, jdemeyer, ncoghlan, njs, xgdomingo, yselivanov
Date 2017-09-09.13:24:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1504963457.09.0.935727692484.issue29988@psf.upfronthosting.co.za>
In-reply-to
Content
After chatting to Facebook's Carl Shapiro here at the core dev sprint, I'm going to start exploring a hopefully more robust white-listing based approach where we check for pending calls in the following cases:

* the instruction pointer either hasn't changed or has gone backwards and the instruction isn't a YIELD_FROM (the "return to the start of a loop" case)
* the next instruction is RETURN_VALUE (the function postamble case)

For now, I'm going to *skip* checking for additional pending calls when exiting a frame via exception, based on the theory that if we're already handling an exception, it's OK to wait until something catches it before checking for potential additional exception sources.
History
Date User Action Args
2017-09-09 13:24:17ncoghlansetrecipients: + ncoghlan, gregory.p.smith, njs, Mark.Shannon, erik.bray, jdemeyer, yselivanov, deleted0524, xgdomingo
2017-09-09 13:24:17ncoghlansetmessageid: <1504963457.09.0.935727692484.issue29988@psf.upfronthosting.co.za>
2017-09-09 13:24:17ncoghlanlinkissue29988 messages
2017-09-09 13:24:16ncoghlancreate