Raymond Hettinger <[EMAIL PROTECTED]> added the comment: Not too excited about this. It adds to compilation time but doesn't save any runtime. It's not at all common for production code to have unreachable code at RAISE_VARARGS or BREAK_LOOP, so I see no reason to complexify to the peepholer to handle this case.
---------- nosy: +rhettinger resolution: -> rejected status: open -> closed _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1764986> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
