GH-145667: Merge GET_ITER and GET_YIELD_FROM_ITER#146120
GH-145667: Merge GET_ITER and GET_YIELD_FROM_ITER#146120markshannon merged 4 commits intopython:mainfrom
GET_ITER and GET_YIELD_FROM_ITER#146120Conversation
…more like FOR_ITER
|
Just to be sure, please run the buildbots |
|
🤖 New build scheduled with the buildbot fleet by @markshannon for commit e3ea233 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F146120%2Fmerge If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again. |
|
🤖 New build scheduled with the buildbot fleet by @markshannon for commit 1b8f043 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F146120%2Fmerge If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again. |
|
Of the 12 failing buildbots, 7 were pre-existing failures and 5 are "new" refleaks. However, since this PR is platform independent, there should be leaks everywhere or nowhere. |
|
Also modifies
SENDto make it a bit more like FOR_ITER as both are now fed byGET_ITER.Apart from saving an opcode, this will enable broadly similar optimizations to be applied to
SENDas are already applied toFOR_ITER. Which will be able to:yield from seqwhereseqis a common iterable, likelist.SENDas it will be mostly specialized.For now, this is broadly performance neutral, between +0% and -1%, mostly about 0%.
GET_ITERandGET_YIELD_FROM_ITERinstructions #145667