This code logs 6
, 6 times:
(function timer() {
for (var i=0; i<=5; i++) {
setTimeout(function clog() {console.log(i)}, i*1000);
}
})();
But this code...
(function timer() {
for (let i=0; i<=5; i++) {
setTimeout(function clog() {console.log(i)}, i*1000);
}
})();
... logs the following result:
0
1
2
3
4
5
Why?
Is it because let
binds to the inner scope each item differently and var
keeps the latest value of i
?
With var
you have a function scope, and only one shared binding for all of your loop iterations - i.e. the i
in every setTimeout callback means the same variable that finally is equal to 6 after the loop iteration ends.
With let
you have a block scope and when used in the for
loop you get a new binding for each iteration - i.e. the i
in every setTimeout callback means a different variable, each of which has a different value: the first one is 0, the next one is 1 etc.
So this:
(function timer() {
for (let i = 0; i <= 5; i++) {
setTimeout(function clog() { console.log(i); }, i * 1000);
}
})();
is equivalent to this using only var:
(function timer() {
for (var j = 0; j <= 5; j++) {
(function () {
var i = j;
setTimeout(function clog() { console.log(i); }, i * 1000);
}());
}
})();
using immediately invoked function expression to use function scope in a similar way as the block scope works in the example with let
.
It could be written shorter without using the j
name, but perhaps it would not be as clear:
(function timer() {
for (var i = 0; i <= 5; i++) {
(function (i) {
setTimeout(function clog() { console.log(i); }, i * 1000);
}(i));
}
})();
And even shorter with arrow functions:
(() => {
for (var i = 0; i <= 5; i++) {
(i => setTimeout(() => console.log(i), i * 1000))(i);
}
})();
(But if you can use arrow functions, there's no reason to use var
.)
This is how Babel.js translates your example with let
to run in environments where let
is not available:
"use strict";
(function timer() {
var _loop = function (i) {
setTimeout(function clog() {
console.log(i);
}, i * 1000);
};
for (var i = 0; i <= 5; i++) {
_loop(i);
}
})();
Thanks to Michael Geary for posting the link to Babel.js in the comments. See the link in the comment for a live demo where you can change anything in the code and watch the translation taking place immediately. It's interesting to see how other ES6 features get translated as well.