Master the JavaScript Interview: What is a Closure?

原文出处 Master the JavaScript Interview: What is a Closure?

Master the JavaScript Interview: What is a Closure?

“Master the JavaScript Interview” is a series of posts designed to prepare candidates for common questions they are likely to encounter when applying for a mid to senior-level JavaScript position. These are questions I frequently use in real interviews.

I’m launching the series with a question that is often my first and last question in my JavaScript interviews. Frankly, you can’t get very far with JavaScript without learning about closures.

You can muck around a bit, but will you really understand how to build a serious JavaScript application? Will you really understand what is going on, or how the application works? I have my doubts. Not knowing the answer to this question is a serious red flag.

Not only should you know the mechanics of what a closure is, you should know why it matters, and be able to easily answer several possible use-cases for closures.

Closures are frequently used in JavaScript for object data privacy, in event handlers and callback functions, and in partial applications, currying, and other functional programming patterns.

I don’t care if a candidate knows the word “closure” or the technical definition. I want to find out if they understand the basic mechanics. If they don’t, it’s usually a clear indicator that the developer does not have a lot of experience building actual JavaScript applications.

If you can’t answer this question, you’re a junior developer. I don’t care how long you’ve been coding.

Be prepared for a quick follow-up: “Can you name two common uses for closures?”

What is a Closure?

In a nutshell, a closure is the combination of a function bundled together (enclosed) with references to it’s surrounding state (the lexical environment). In JavaScript, closures are created every time a function is created, at function creation time.

Those are the basic mechanics, but why do we care? In practical terms, since a closure bundles the lexical environment, a closure gives you access to an outer function’s scope from an inner function.

To use a closure, simply define a function inside another function and expose it. To expose a function, return it or pass it to another function.

The inner function will have access to the variables in the outer function scope, even after the outer function has returned.

Using Closures (Examples)

Among other things, closures are commonly used to give objects data privacy. Data privacy is an essential property that helps us program to an interface, not an implementation. This is an important concept that helps us build more robust software because implementation details are more likely to change in breaking ways than interface contracts.

“Program to an interface, not an implementation.” Design Patterns: Elements of Reusable Object Oriented Software

In JavaScript, closures are the primary mechanism used to enable data privacy. When you use closures for data privacy, the enclosed variables are only in scope within the containing (outer) function. You can’t get at the data from an outside scope except through the object’s privileged methods. In JavaScript, any exposed method defined within the closure scope is privileged. For example:

Play with this in JSBin. _(Don’t see any output? Copy and paste _this HTML_ into the HTML pane.)_

In the example above, the .get() method is defined inside the scope of getSecret(), which gives it access to any variables from getSecret(), and makes it a privileged method. In this case, the parameter, secret.

Objects are not the only way to produce data privacy. Closures can also be used to create stateful functions whose return values may be influenced by their internal state, e.g.:

const secret = (msg) => () => msg;

Available on JSBin. _(Don’t see any output? Copy and paste _this HTML_ into the HTML pane.)_

In functional programming, closures are frequently used for partial application & currying. This requires some definitions:

Application: The process of applying a function to its arguments in order to produce a return value.

Partial Application: The process of applying a function to some of its arguments. The partially applied function gets returned for later use. In other words, a function that takes a function with multiple parameters and returns a function with fewer parameters. Partial application _fixes _(partially applies the function to) one or more arguments inside the returned function, and the returned function takes the remaining parameters as arguments in order to complete the function application.

Partial application takes advantage of closure scope in order to fix parameters. You can write a generic function that will partially apply arguments to the target function. It will have the following signature:

partialApply(targetFunction: Function, ...fixedArgs: Any[]) =>
  functionWithFewerParams(...remainingArgs: Any[])

If you need help reading the signature above, check out Rtype: Reading Function Signatures.

It will take a function that takes any number of arguments, followed by arguments we want to partially apply to the function, and returns a function that will take the remaining arguments.

An example will help. Say you have a function that adds two numbers:

const add = (a, b) => a + b;

Now you want a function that adds 10 to any number. We’ll call it add10(). The result of add10(5) should be 15. Our partialApply() function can make that happen:

const add10 = partialApply(add, 10);

In this example, the argument, 10 becomes a fixed parameter remembered inside the add10() closure scope.

Let’s look at a possible partialApply() implementation:

Available on JSBin. _(Don’t see any output? Copy and paste _this HTML_ into the HTML pane.)_

As you can see, it simply returns a function which retains access to the fixedArgs arguments that were passed into the partialApply() function.

Your Turn

What do you use closures for? Send me a response with your favorite use-case, examples, etc…

Level up your skills with courses & webcasts on ES6, TDD, prototypal OO, React, & More.

Eric Elliott_ is the author of _“Programming JavaScript Applications”_ (O’Reilly), and _“Learn Universal JavaScript App Development with Node & React”_. He has contributed to software experiences for _Adobe Systems_, _Zumba Fitness_, _The Wall Street Journal_, _ESPN_, _BBC_, and top recording artists including _Usher_,_Frank Ocean_, _Metallica, and many more.

He spends most of his time in the San Francisco Bay Area with the most beautiful woman in the world.