{"id":3871,"date":"2022-08-20T21:17:50","date_gmt":"2022-08-20T15:47:50","guid":{"rendered":"https:\/\/jassweb.com\/solved\/solved-how-do-javascript-closures-work\/"},"modified":"2022-08-20T21:17:50","modified_gmt":"2022-08-20T15:47:50","slug":"solved-how-do-javascript-closures-work","status":"publish","type":"post","link":"https:\/\/jassweb.com\/solved\/solved-how-do-javascript-closures-work\/","title":{"rendered":"(Solved) How do JavaScript closures work?"},"content":{"rendered":"

[ad_1]
\n<\/p>\n

\n
\n
<\/div>\n
\n
\n

A closure is a pairing of:<\/p>\n

    \n
  1. A function and<\/li>\n
  2. A reference to that function’s outer scope (lexical environment)<\/li>\n<\/ol>\n

    A lexical environment is part of every execution context (stack frame) and is a map between identifiers (i.e. local variable names) and values.<\/p>\n

    Every function in JavaScript maintains a reference to its outer lexical environment. This reference is used to configure the execution context created when a function is invoked. This reference enables code inside the function to “see” variables declared outside the function, regardless of when and where the function is called.<\/p>\n

    If a function was called by a function, which in turn was called by another function, then a chain of references to outer lexical environments is created. This chain is called the scope chain.<\/p>\n

    In the following code, inner<\/code> forms a closure with the lexical environment of the execution context created when foo<\/code> is invoked, closing over<\/em> variable secret<\/code>:<\/p>\n<\/p>\n

    \n
    \n
    function foo() {\n  const secret = Math.trunc(Math.random() * 100)\n  return function inner() {\n    console.log(`The secret number is ${secret}.`)\n  }\n}\nconst f = foo() \/\/ `secret` is not directly accessible from outside `foo`\nf() \/\/ The only way to retrieve `secret`, is to invoke `f`<\/code><\/pre>\n<\/div>\n<\/div>\n
    In other words: in JavaScript, functions carry a reference to a private “box of state”, to which only they (and any other functions declared within the same lexical environment) have access. This box of the state is invisible to the caller of the function, delivering an excellent mechanism for data-hiding and encapsulation.<\/p>\n
    And remember: functions in JavaScript can be passed around like variables (first-class functions), meaning these pairings of functionality and state can be passed around your program: similar to how you might pass an instance of a class around in C++.<\/p>\n
    If JavaScript did not have closures, then more states would have to be passed between functions explicitly<\/em>, making parameter lists longer and code noisier.<\/p>\n
    So, if you want a function to always have access to a private piece of state, you can use a closure.<\/p>\n
    …and frequently we do<\/em> want to associate the state with a function. For example, in Java or C++, when you add a private instance variable and a method to a class, you are associating the state with functionality.<\/p>\n
    In C and most other common languages, after a function returns, all the local variables are no longer accessible because the stack-frame is destroyed. In JavaScript, if you declare a function within another function, then the local variables of the outer function can remain accessible after returning from it. In this way, in the code above, secret<\/code> remains available to the function object inner<\/code>, after<\/em> it has been returned from foo<\/code>.<\/p>\n
    Uses of Closures<\/h2>\n
    Closures are useful whenever you need a private state associated with a function. This is a very common scenario – and remember: JavaScript did not have a class syntax until 2015, and it still does not have a private field syntax. Closures meet this need.<\/p>\n
    Private Instance Variables<\/h3>\n
    In the following code, the function toString<\/code> closes over the details of the car.<\/p>\n<\/p>\n
    \n
    \n
    function Car(manufacturer, model, year, color) {\n  return {\n    toString() {\n      return `${manufacturer} ${model} (${year}, ${color})`\n    }\n  }\n}\n\nconst car = new Car('Aston Martin', 'V8 Vantage', '2012', 'Quantum Silver')\nconsole.log(car.toString())<\/code><\/pre>\n<\/div>\n<\/div>\n
    Functional Programming<\/h3>\n
    In the following code, the function inner<\/code> closes over both fn<\/code> and args<\/code>.<\/p>\n<\/p>\n
    \n
    \n
    function curry(fn) {\n  const args = []\n  return function inner(arg) {\n    if(args.length === fn.length) return fn(...args)\n    args.push(arg)\n    return inner\n  }\n}\n\nfunction add(a, b) {\n  return a + b\n}\n\nconst curriedAdd = curry(add)\nconsole.log(curriedAdd(2)(3)()) \/\/ 5<\/code><\/pre>\n<\/div>\n<\/div>\n
    Event-Oriented Programming<\/h3>\n
    In the following code, function onClick<\/code> closes over variable BACKGROUND_COLOR<\/code>.<\/p>\n<\/p>\n
    \n
    \n
    const $ = document.querySelector.bind(document)\nconst BACKGROUND_COLOR = 'rgba(200, 200, 242, 1)'\n\nfunction onClick() {\n  $('body').style.background = BACKGROUND_COLOR\n}\n\n$('button').addEventListener('click', onClick)<\/code><\/pre>\n
    <button>Set background color<\/button><\/code><\/pre>\n<\/div>\n<\/div>\n
    Modularization<\/h3>\n
    In the following example, all the implementation details are hidden inside an immediately executed function expression. The functions tick<\/code> and toString<\/code> close over the private state and functions they need to complete their work. Closures have enabled us to modularize and encapsulate our code.<\/p>\n<\/p>\n
    \n
    \n
    let namespace = {};\n\n(function foo(n) {\n  let numbers = []\n\n  function format(n) {\n    return Math.trunc(n)\n  }\n\n  function tick() {\n    numbers.push(Math.random() * 100)\n  }\n\n  function toString() {\n    return numbers.map(format)\n  }\n\n  n.counter = {\n    tick,\n    toString\n  }\n}(namespace))\n\nconst counter = namespace.counter\ncounter.tick()\ncounter.tick()\nconsole.log(counter.toString())<\/code><\/pre>\n<\/div>\n<\/div>\n
    Examples<\/h2>\n
    Example 1<\/h3>\n
    This example shows that the local variables are not copied in the closure: the closure maintains a reference to the original variables themselves<\/em>. It is as though the stack-frame stays alive in memory even after the outer function exits.<\/p>\n<\/p>\n
    \n
    \n
    function foo() {\n  let x = 42\n  let inner = () => console.log(x)\n  x = x + 1\n  return inner\n}\n\nfoo()() \/\/ logs 43<\/code><\/pre>\n<\/div>\n<\/div>\n
    Example 2<\/h3>\n
    In the following code, three methods log<\/code>, increment<\/code>, and update<\/code> all close over the same lexical environment.<\/p>\n
    And every time createObject<\/code> is called, a new execution context (stack frame) is created and a completely new variable x<\/code>, and a new set of functions (log<\/code> etc.) are created, that close over this new variable.<\/p>\n<\/p>\n
    \n
    \n
    function createObject() {\n  let x = 42;\n  return {\n    log() { console.log(x) },\n    increment() { x++ },\n    update(value) { x = value }\n  }\n}\n\nconst o = createObject()\no.increment()\no.log() \/\/ 43\no.update(5)\no.log() \/\/ 5\nconst p = createObject()\np.log() \/\/ 42<\/code><\/pre>\n<\/div>\n<\/div>\n
    Example 3<\/h3>\n
    If you are using variables declared using var<\/code>, be careful you understand which variable you are closing over. Variables declared using var<\/code> are hoisted. This is much less of a problem in modern JavaScript due to the introduction of let<\/code> and const<\/code>.<\/p>\n
    In the following code, each time around the loop, a new function inner<\/code> is created, which closes over i<\/code>. But because var i<\/code> is hoisted outside the loop, all of these inner functions close over the same variable, meaning that the final value of i<\/code> (3) is printed, three times.<\/p>\n<\/p>\n
    \n
    \n
    function foo() {\n  var result = []\n  for (var i = 0; i < 3; i++) {\n    result.push(function inner() { console.log(i) } )\n  }\n\n  return result\n}\n\nconst result = foo()\n\/\/ The following will print `3`, three times...\nfor (var i = 0; i < 3; i++) {\n  result[i]() \n}<\/code><\/pre>\n<\/div>\n<\/div>\n
    Final points:<\/h2>\n