Message79848
> Your change to the "LOAD_CONST trueconst JUMP_IF_FALSE xx POP_TOP"
> optimization doesn't preserve the optimization to:
> def f():
> return 1 and a
> I suspect we don't care since "0 or a" wasn't optimized.
Yes, this optimization seems meant for "while 1" and "while True" mainly
(which my patch preserves, but I might add a comment).
> I wonder what the "POP_TOP JUMP_FORWARD 1 POP_TOP" was ever for. Why did
> compiler_comprehension_generator() emit it in the first place?
I'm as clueless as you... |
|
Date |
User |
Action |
Args |
2009-01-14 11:17:45 | pitrou | set | recipients:
+ pitrou, collinwinter, rhettinger, jyasskin |
2009-01-14 11:17:44 | pitrou | link | issue4715 messages |
2009-01-14 11:17:44 | pitrou | create | |
|