[issue37500] 3.8.0b2 no longer optimizes away "if 0:" ?

Pablo Galindo Salgado report at bugs.python.org
Fri Jul 5 18:49:24 EDT 2019


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

> It's the expected result of fixing a bug _by_ eliminating the optimization entirely. 

Using jumps is not removing the optimization entirely, is just a weaker and more incomplete way of doing the same. The optimization introduced the bug in the first place. If this was done today it would have been reverted. The only thing legitimating the "error" is time. But this is basically elevating a bug to a feature, making this even more relevant than ever:

https://xkcd.com/1172/

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37500>
_______________________________________


More information about the Python-bugs-list mailing list