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 Mark.Shannon
Recipients Mark.Shannon, nedbat, rhettinger, serhiy.storchaka
Date 2020-12-22.11:41:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1608637313.53.0.133081929271.issue42693@roundup.psfhosted.org>
In-reply-to
Content
What is the problem with NOPs?
If there are performance regressions in real code, then that needs to be addressed. 
If only in a few toy examples, then that is (IMO) a price worth paying for predictable debugging and profiling.

Raymond:
   Effectively it does cease to exist. A NOP in the bytecode, except maybe in the tightest of loops, is going to be impossible to detect without inspecting the bytecode.

Serhiy:
   The NOP is outside of the loop, so won't slow down the loop.
History
Date User Action Args
2020-12-22 11:41:53Mark.Shannonsetrecipients: + Mark.Shannon, rhettinger, nedbat, serhiy.storchaka
2020-12-22 11:41:53Mark.Shannonsetmessageid: <1608637313.53.0.133081929271.issue42693@roundup.psfhosted.org>
2020-12-22 11:41:53Mark.Shannonlinkissue42693 messages
2020-12-22 11:41:53Mark.Shannoncreate