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 terry.reedy
Recipients Dennis Sweeney, Mark.Shannon, corona10, eric.smith, rhettinger, shihai1991, terry.reedy
Date 2020-06-13.10:24:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1592043842.08.0.729182569797.issue40925@roundup.psfhosted.org>
In-reply-to
Content
I could understand wanting to replace TOP,...,FOURTH with PEEK(n) and the SET_XYZs with the now deleted SET(_VALUE)(n, v), but to me, replacing PEEK-SET with POPs and PUSHes (in different orders) that directly mean something different but that compilers (all?) optimize to mean the same thing makes the code initially harder to read.  In particular, the old version of TARGET(ROT_FOUR) is initially clearer without thinking through the effect of the particular order of pushes in the new version.  It depends on what one is accustomed to.
History
Date User Action Args
2020-06-13 10:24:02terry.reedysetrecipients: + terry.reedy, rhettinger, eric.smith, Mark.Shannon, corona10, Dennis Sweeney, shihai1991
2020-06-13 10:24:02terry.reedysetmessageid: <1592043842.08.0.729182569797.issue40925@roundup.psfhosted.org>
2020-06-13 10:24:02terry.reedylinkissue40925 messages
2020-06-13 10:24:01terry.reedycreate