js> (function() { for(let x in []) let {} = [1]; }) function () { for (let x in []) { let [] = [1]; } }

Of course, this exists only given 'for (let x...)' and equivalent let bindings in for loop initial parts, and for-in loop left-hand sides. Such bindings make a block scope around the loop body (and condition and update parts, if for rather than for-in). This means the decompilation is not accurate, but it does not mean the for loop's enclosing scope is polluted by the let in the body. E.g., in for (let x in [1,2,3]) let y = x*x y does not escape the loop body's implicit block scope. /be

Comment on attachment 295586 [details] [diff] [review] fix @@ -3194,17 +3195,18 @@ Statement(JSContext *cx, JSTokenStream * the comment described what the old if did, afaict it no longer describes the current logic.

Thanks, timeless! /be

Fixed: js/src/jsemit.h 3.88 js/src/jsparse.c 3.322 /be

The following also required updating now that this is fixed. /cvsroot/mozilla/js/tests/js1_7/extensions/regress-346642-06.js,v new revision: 1.4; previous revision: 1.3

v