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 selik
Recipients methane, remi.lapeyre, rhettinger, selik, serhiy.storchaka
Date 2018-06-08.17:54:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1528480473.4.0.592728768989.issue33462@psf.upfronthosting.co.za>
In-reply-to
Content
It looks like there's general agreement on python-dev that this is appropriate for v3.8 (not v3.7).

Guido van Rossum and Ramsey D'silva gave a +1. Raymond Hettinger noted some use cases. INADA Naoki raised a point about waiting for other implementations, which Guido agreed with, but after some research came around to OK'ing this for v3.8.

Responding to Serhiy Storchaka's worry about adding new code possibly upsetting the compiler optimizations: The implementation seems straightforward and unlikely to confuse the compiler. Is there evidence that similar code has previously made CPython slower? If the compiler's black magic is too difficult to understand, it may be equally plausible that this code causes an improvement to the optimization of unrelated code.
History
Date User Action Args
2018-06-08 17:54:33seliksetrecipients: + selik, rhettinger, methane, serhiy.storchaka, remi.lapeyre
2018-06-08 17:54:33seliksetmessageid: <1528480473.4.0.592728768989.issue33462@psf.upfronthosting.co.za>
2018-06-08 17:54:33seliklinkissue33462 messages
2018-06-08 17:54:33selikcreate