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 brett.cannon
Recipients brett.cannon, dino.viehland, serhiy.storchaka, steve.dower, vstinner
Date 2016-12-10.19:50:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481399435.0.0.868721915784.issue28924@psf.upfronthosting.co.za>
In-reply-to
Content
Inlining wouldn't break Pyjion since all of its smarts would be in the trampoline function in PyInterpreterState. It may break other debuggers like Python Tools for Visual Studio, though (+steve.dower for that).

But is the overhead honestly that high to warrant inlining? What kind of perf gain do you see from doing this? My worry is that if the perf isn't that much better that inlining will simply make it harder to tweak that function in the future.
History
Date User Action Args
2016-12-10 19:50:35brett.cannonsetrecipients: + brett.cannon, vstinner, dino.viehland, serhiy.storchaka, steve.dower
2016-12-10 19:50:34brett.cannonsetmessageid: <1481399435.0.0.868721915784.issue28924@psf.upfronthosting.co.za>
2016-12-10 19:50:34brett.cannonlinkissue28924 messages
2016-12-10 19:50:34brett.cannoncreate