Incorrect assignement behaviour in 'let' to 'for' loop variable

[susano]

One would expect x to be 42, like y at that point of the program.

for x in [10]
  y = 10
  let
    x := 42
    y := 42
  console.log("x : #x") # => 10
  console.log("y : #y") # => 42

[vendethiel]

Should we remove auto-infusing IIFEs ?

Just FTR, this comes from Coco, when we didn't have for let, you'd just be able to capture loop vars doing

for x in [10] then let
 qS "#el-#{x}" .onclick = -> alert x

I don't think this feature is heavily used and we can probably remove it now that we have saud for let.
Thoughts ?

[robotlolita]

Any reason why x is even captured in this code?

var i$, ref$, len$, x, y;
for (i$ = 0, len$ = (ref$ = [10]).length; i$ < len$; ++i$) {
  x = ref$[i$];
  y = 10;
  (fn$.call(this, x));
  console.log("x : " + x);
  console.log("y : " + y);
}
function fn$(x){
  x = 42;
  y = 42;
}

[vendethiel]

As I said, it's called Auto-infusing IIFEs and was used to auto-capture loop vars with let.

[robotlolita]

I see, yeah, I don't think that feature is really needed with for let, and it makes things weird.