2 ms·
Thanks for the replies. I really wasn't aware of the behavior of let here and did indeed learn something. The "buggy" code really does work. It's important to
by xg15 6y ago
Thanks for the replies. I really wasn't aware of the behavior of let here and did indeed learn something. The "buggy" code really does work.
It's important to note that this is not just due to scoping but that a regular for loop apparently really makes copies of its environment for each iteration, as ylyn described[1].
You can demonstrate this as follows:
const objs = [];
for (let i = 0; i < 3; i++) { // i++ seems to be executed after copying but before execution of the loop body.
objs.push({
getI() {return i},
add10() {i += 10}
});
}
// each object gets a copy of i from its respective iteration:
console.info(objs[0].getI(), objs[1].getI(), objs[2].getI()); // prints 0 1 2
// the copies can be modified independently:
objs[0].add10();
objs[2].add10();
console.info(objs[0].getI(), objs[1].getI(), objs[2].getI()); // prints 10 1 12
I'm not sure I like this design, to be honest. This is an awfully complex special case hidden in something as mundane-looking as a regular for loop.
Seems to me, this can make understanding the general principles behind scopes and environments harder at the expense of making a particular special case more convenient.
[1] https://news.ycombinator.com/item?id=23955809 https://news.ycombinator.com/item?id=23955809
- johnfn 6y agoThis seems pretty standard to me. Could you produce an example of a language which doesn't have this behavior? EDIT: I think I understand your confusion. You've gotten confused because you're expecting `y = 5; let x = y` be able to hold a reference to `y` the number in the same way that `y = {}; let x = y` holds a reference to y the object. But that's honestly the behavior of practically every language I could name - numbers and other small values that can fit in a register are always copied. You can see the referential behavior if you change your `i` to an object: let result = [] for (let obj = {}; Object.keys(obj).length < 3; obj[Math.random()] = "hello") { result.push(obj); } console.log(result); // notice all 3 entries in the array are the same But yeah - JavaScript does nothing special in either of these cases. Similar code will get you similar results across any language I could name. The only way to get around it would be to manually mark your numeric i as a reference in a language that has them, like C/C++/Rust.
- tomxor 6y agoThe confusion is not about assignment behavior, it's about block scopes, specifically within the for loop. Before JS had `let` and `const` there was no built in way of obtaining a block scope (for, if, else, while, do and {}), you had to obtain one artificially by passing variables into a function scope, e.g a predefined function or an IIFE. I'm talking about `var`... paste this into your browsers console, you get 8 logged 8 times: for (var i = 0; i < 8; i ++) { setTimeout(() => { console.log(i) }, 100); } I'm pretty sure this is the issue the OP was trying to demonstrate. With `var` i is _not_ bound to the for loop scope, it's bound the closest parent function scope. The key difference is not only that i can be accessed after the for loop, but that there is only one parent function scope, so i is effectively overwritten - whereas if i was bound to the for block there would be a separate scope for each iteration. Since the timeout function has no i in it's scope it walks up the parent scopes, it can only find i in the parent function scope and by the time it has executed it will be whatever the last iteration assigned it - or even more confusingly what something after the loop assigned it. This is why `let` was added: for (let i = 0; i < 8; i ++) { setTimeout(() => { console.log(i) }, 100); } Which gives you 0 through 7 let assigns i to the for loop's scope, with a different one for each iteration, this preserves the local context the setTimeout function was defined in which is intuitive and what people expect. Another nice thing that people forget with this feature (including myself out of habbit) is that you can now replace IIFEs with block scope literals {} (provided you stop using var, which you should have anyway) In short, var was a nightmare, it's only benefit is obfuscation, it was the source of countless needless bugs, and that's why we now have const/let and block scopes.
- xg15 6y agoYes, exactly. I think what was confusing to me here is the interaction between child environments in for(;;). Usually, scopes in JS work like the OP link describes them: If a block is entered, a child environment is created that has a reference to its parent environment. A variable either belongs to the parent and is shared with all children - or belongs to one particular child and is initialised through assignment. However different child environments can never influence each other. for(;;) does something different: It takes one child environment (of iteration n) and clones it for iteration n+1. The effect is that there is a single let i = ... statement which leads to the creation of several independent variables. It's easy to see why this was done - it's the only way how you can have both mutating statements like i++ and closures that capture state from a particular iteration - but I'm not aware this is done anywhere else in JS.
- hencq 6y agoThe book Crafting Interpreters has a design note specifically about this special case [0] and how different languages handle it: > The increment clause really does look like mutation. That implies there is a single variable that’s getting updated each step. But it’s almost never useful for each iteration to share a loop variable. The only time you can even detect this is when closures capture it. And it’s rarely helpful to have a closure that references a variable whose value is whatever value caused you to exit the loop. > The pragmatically useful answer is probably to do what JavaScript does with let in for loops. Make it look like mutation but actually create a new variable each time because that’s what users want. It is kind of weird when you think about it, though. [0] https://craftinginterpreters.com/closures.html#design-note https://craftinginterpreters.com/closures.html#design-note