Message267768
Attaching forbegin3.patch. It reintroduces GET_ITER for the sole purpose of eagerly throwing. I decided to reuse GET_ITER over something like TEST_ITER as this way we can have GET_ITER flow into FOR_BEGIN & rely on the fast path of iter(iter(x))
GET_ITER/JUMP_FORWARD idea doesn't work because FOR_ITER is carefully setup currently to trace as existing on 2 separate lines. If we JUMP_FORWARD into FOR_ITER then that tracing triggers & our trace will say we executed the last line of the loop immediately before executing the iteration logic |
|
Date |
User |
Action |
Args |
2016-06-08 03:38:19 | Demur Rumed | set | recipients:
+ Demur Rumed, rhettinger, dino.viehland, serhiy.storchaka |
2016-06-08 03:38:18 | Demur Rumed | set | messageid: <1465357098.22.0.988148815374.issue27127@psf.upfronthosting.co.za> |
2016-06-08 03:38:18 | Demur Rumed | link | issue27127 messages |
2016-06-08 03:38:18 | Demur Rumed | create | |
|