Unlock this lesson and all 986 of the free egghead.io lessons, plus get JavaScript content delivered directly to your inbox!

# What is JavaScript Function Currying?

5:34 JavaScript lesson by

Currying is a core concept of functional programming and a useful tool for any developer's toolbelt. In this lesson, John walks through the definition of currying and its practical usage.

Get the Code Now
click to level up

Currying is a core concept of functional programming and a useful tool for any developer's toolbelt. In this lesson, John walks through the definition of currying and its practical usage.

Srihari

best and easiest to understand explanation for how to practically use currying... thank you

David

Great video!

Trying to wrap my brain around other practical applications for using curry in my day to day.

Any suggestions of other typical scenarios where currying might come in handy?

Thanks

Fully answering your question is beyond the scope a of single comment, but currying is a core concept of functional programming. Writing in a functional-style is applicable to everything in your day-to-day. Instead of writing monolithic functions that don't return anything, imagine writing your application in a bunch of tiny functions each returning a something that you can use to compose together more complex functions.

It's a complete change in the way of thinking about writing code, so don't worry if it doesn't click right away.

Watch this, I think it will give you a better idea: https://egghead.io/lessons/javascript-advanced-reduce-composing-functions-with-reduce

You may think it's a little weird to write a function which you would call and then call with that returns and then call with that returns. It'd be like one, two, and three where the implementation would be my function is a single argument. That's going to return another function with an argument and another one. Then, all of that combined would be A plus B plus C.

Basically, these line up this one and this A and this two and this B and this three and this C, and we add them altogether. You would see the result of this is just going to be result. Hit Save. We get six since that's just one plus two three.

Where this gets interesting to you is when you do, we'll change this to A, add event listener and then B will be our element and then add our callback which is an event which says event.target.style.backgroundcolor equals C, and delete this down here.

Now, instead of one, two, and three, we'll look up our element which we have one here and we'll say one click and the color red. We don't need this. We don't need that. Now, hit Save. When I click on this, it turns red.

Now, where this gets really interesting is if I take all of these off and I instead just return a function. I'll call this one event color. Now, in my one event color function, I can call mouse over and blue. Hit Save. I'll come over and mouse over this and it turns blue.

Our original function definition hasn't changed at all. We still have A, B, C which is A, B, and C which is now A, B, and C. It's just that at this point, now we can do things like two, two, and two event color, say mouse out and green. Hit Save.

We'll mouse out of two and mouse into one. We've created functions that represent what we want to do. We just have to pass in the event and the color.

We can make this style of program even easier by using libraries like Ramda which I've imported as R. Instead of this style where it's parameter, function, parameter, function, parameter, function, I'll just delete all of that. Say R curry and that's going to take a function where I can say A, B, C and then the function block inside of there can be our original function block. I'll hit Save and you'll see that it still works the same.

Because our signature here is actually different, it's just three parameters, I can say F and then one and then click and then purple. Hit Save. I'll come and click one and it turns purple because now it's just three parameters. I don't have to call that function, calling function, calling function.

Where this gets amazing is doing things with placeholders where I say R dot underscore, underscore. That's a placeholder which means that now we can have a click purple function. That's expecting one more parameter which is this placeholder.

We can say click purple one and click purple two. It's going to pass one and two in as this missing placeholder parameter. When I come in and click on one and click on two, we've turned each of those elements purple.

You can even put in multiple placeholders. If I turn this into a placeholder, and I'll rename this from click purple to just click. Come down here, say one, green, two, orange, hit Save. Click on one, click on two, and we have a great, little function where we just pass in an element and a color and it handles everything else for us.

This is what currying allows us to do. It allows to break apart these pieces like A, B, and C from the implementation or the block inside of our function, pull them out into parameters and then pull those out into individual functions where we can add things like placeholders and create additional functions from those. It gives us a crazy amount of flexibility to create any sort of function to represent what's going on inside of here.

While the definition of currying is just breaking down a function that takes multiple arguments into functions that can take one or more of those arguments. The actual definition isn't as important as realizing what it allows you to do when pulling apart these arguments into individual functions and making them these reusable pieces of logic.

The last thing to note is that you could write your own curry function. Its implementation is only a few lines of code and it's available in a few libraries. Currying is also built in to other functional programming languages. That's why it might be a bit difficult to wrap your head around what's going on when you're not used to reading functions in this curried style.

Featured course:

#### Get Started with Elasticsearch

HEY, QUICK QUESTION!