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 serhiy.storchaka
Recipients lukasz.langa, petr.viktorin, pitrou, rhettinger, serhiy.storchaka, skrah, vstinner
Date 2020-07-08.07:11:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1594192286.49.0.639098415653.issue39542@roundup.psfhosted.org>
In-reply-to
Content
I do not know the purpose of this issue. The new code does not look cleaner to me, but maybe it is only for me.

But performance regressions should be fixed. We cannot rely on compiler-specific global optimization, which is hard to test and does not work for dynamic linkage (third-party extensions and applications with built-in Python). Even "inline" is just a hint to the compiler and does not guarantee inlining the code.

Raymond's suggestions look reasonable to me.
History
Date User Action Args
2020-07-08 07:11:26serhiy.storchakasetrecipients: + serhiy.storchaka, rhettinger, pitrou, vstinner, petr.viktorin, skrah, lukasz.langa
2020-07-08 07:11:26serhiy.storchakasetmessageid: <1594192286.49.0.639098415653.issue39542@roundup.psfhosted.org>
2020-07-08 07:11:26serhiy.storchakalinkissue39542 messages
2020-07-08 07:11:26serhiy.storchakacreate