WTF is a Closure?

I know what the closure means but still the last example [1].map((a)) => a) is not quite clear.

Its callback is a closure because it's a nested function within a function that has access to its parent's scopes.

It would be if Tyler has provided more explanation to the quoted statement with regard to the given example in my opinion.

It would be if Tyler has provided more explanation to the quoted statement with regard to the given example in my opinion.

Anytime a function is passed as a callback argument to another function, that callback will be executed at some point within the containing function's body. Just the same as if it were defined inside of that containing function just like the example in the lesson. Which means it is a nested function with access to any variables defined inside of it, the containing parent function, and the global scope. This is why the callback arg is a closure.

Thanks for a rapid response Tyler.

No problem!

Which means it is a nested function with access to any variables defined inside of it, the containing parent function, and the global scope. This is why the callback arg is a closure.

I do understand your point of view, but I'd argue that the callback function should not only HAVE the possibility to access to any variables containing the parent context, but actually BE accessing any variables defined in the parent context (since the variables defined in the parent context would be garbage collected, unless used by the callback function).

e.g. [1, 2, 3].map((value) => { console.log('I am a callback function not actually using any variables defined within my parent scope'); });

is NOT a closure, at least from my point of view, since it does not actually access (thus close upon) any of the variables defined within the parent context.

In your example, [1].map((a) => a) the callback function uses the a variable that was defined within its own scope, not a variable defined in the parent scope.

Am I missing anything here?

but actually BE accessing any variables defined in the parent context

The actual implementation of a closure is different depending on the language you are programming in. Here is what MDN says about closures in JavaScript:

A closure is the combination of a function bundled together (enclosed) with references to its surrounding state (the lexical environment). In other words, a closure gives you access to an outer function’s scope from an inner function. In JavaScript, closures are created every time a function is created, at function creation time.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Closures

What's interesting to me is that last line.

In JavaScript, closures are created every time a function is created, at function creation time.

The safe bet for sure is that the inner function should be referencing something in it's parent's scope in order to remove any doubt of being considered a closure. However, I have heard both sides of this answer, which again, also depends on the programming language.

I'm not really sure what the takeaway of understanding what a closure is. It seems like we implicitly understand what a closure as very early one when learning javascript - and the idea of the function scope.

Can you clear up why this term is so important to understand?

This a good question Jon. Closures can trip us up, for instance with loops, if we're not careful to recognize them and how they work. On the other hand, they are also an immensely powerful tool, enabling patterns like modules in their various forms.

My takeaway from this lesson: noticing that closure is all around us in JavaScript. That it's not a new syntax or patterns that we must learn, but instead a skill that we must develop (recognize, embrace, and leverage).

The enlightenment moment should be: oh, closures are already occurring all over my code, I can finally see them now.