JavaScript curry: what are the practical applications?

@Hank Gay

In response to EmbiggensTheMind's comment:

I can't think of an instance where currying—by itself—is useful in JavaScript; it is a technique for converting function calls with multiple arguments into chains of function calls with a single argument for each call, but JavaScript supports multiple arguments in a single function call.

In JavaScript—and I assume most other actual languages (not lambda calculus)—it is commonly associated with partial application, though. John Resig explains it better, but the gist is that have some logic that will be applied to two or more arguments, and you only know the value(s) for some of those arguments.

You can use partial application/currying to fix those known values and return a function that only accepts the unknowns, to be invoked later when you actually have the values you wish to pass. This provides a nifty way to avoid repeating yourself when you would have been calling the same JavaScript built-ins over and over with all the same values but one. To steal John's example:

String.prototype.csv = String.prototype.split.partial(/,\s*/);var results = "John, Resig, Boston".csv();alert( (results[1] == "Resig") + " The text values were split properly" );

Agreeing with Hank Gay - It's extremely useful in certain true functional programming languages - because it's a necessary part. For example, in Haskell you simply cannot take multiple parameters to a function - you cannot do that in pure functional programming. You take one param at a time and build up your function. In JavaScript it's simply unnecessary, despite contrived examples like "converter". Here's that same converter code, without the need for currying:

var converter = function(ratio, symbol, input) {return (input*ratio).toFixed(2) + " " + symbol;}var kilosToPoundsRatio = 2.2;var litersToUKPintsRatio = 1.75;var litersToUSPintsRatio = 1.98;var milesToKilometersRatio = 1.62;converter(kilosToPoundsRatio, "lbs", 4); //8.80 lbsconverter(litersToUKPintsRatio, "imperial pints", 2.4); //4.20 imperial pintsconverter(litersToUSPintsRatio, "US pints", 2.4); //4.75 US pintsconverter(milesToKilometersRatio, "km", 34); //55.08 km

I badly wish Douglas Crockford, in "JavaScript: The Good Parts", had given some mention of the history and actual use of currying rather than his offhanded remarks. For the longest time after reading that, I was boggled, until I was studying Functional programming and realized that's where it came from.

After some more thinking, I posit there is one valid use case for currying in JavaScript: if you are trying to write using pure functional programming techniques using JavaScript. Seems like a rare use case though.

I found functions that resemble python's functools.partial more useful in JavaScript:

function partial(fn) {return partialWithScope.apply(this,Array.prototype.concat.apply([fn, this],Array.prototype.slice.call(arguments, 1)));}function partialWithScope(fn, scope) {var args = Array.prototype.slice.call(arguments, 2);return function() {return fn.apply(scope, Array.prototype.concat.apply(args, arguments));};}

Why would you want to use it? A common situation where you want to use this is when you want to bind this in a function to a value:

var callback = partialWithScope(Object.function, obj);

Now when callback is called, this points to obj. This is useful in event situations or to save some space because it usually makes code shorter.

Currying is similar to partial with the difference that the function the currying returns just accepts one argument (as far as I understand that).

Consider filter function. And you want to write a callback for it.

let x = [1,2,3,4,5,6,7,11,12,14,15];let results = x.filter(callback);

Assume want to output only even numbers, so:

let callback = x => x % 2 === 0;

Now imagine we want to implement our callback such thatdepending on scenario it outputs even numbers which are above some threshold number (suchnumber should be configurable).

We can't easily make such threshold number a parameter to callback function, because filter invokes callback and by default passes it array elements and index.

How would you implement this?

This is a good use case for currying:

let x = [1,2,3,4,5,6,7,11,12,14,15];let callback = (threshold) => (x) => (x % 2==0 && x > threshold);let results1 = x.filter(callback(5)); // Even numbers higher than 5let results2 = x.filter(callback(10)); // Even numbers higher than 10console.log(results1,results2);

I know its old thread but I will have to show how this is being used in javascript libraries:

I will use lodash.js library to describe these concepts concretely.

Example:

var fn = function(a,b,c){ return a+b+c+(this.greet || ‘'); }

Partial Application:

var partialFnA = _.partial(fn, 1,3);

Currying:

var curriedFn = _.curry(fn);

Binding:

var boundFn = _.bind(fn,object,1,3 );//object= {greet: ’!'}

usage:

curriedFn(1)(3)(5); // gives 9 or curriedFn(1,3)(5); // gives 9 or curriedFn(1)(_,3)(2); //gives 9partialFnA(5); //gives 9boundFn(5); //gives 9!

difference:

after currying we get a new function with no parameters pre bound.

after partial application we get a function which is bound with some parameters prebound.

in binding we can bind a context which will be used to replace ‘this’, if not bound default of any function will be window scope.

Advise: There is no need to reinvent the wheel. Partial application/binding/currying are very much related. You can see the difference above. Use this meaning anywhere and people will recognise what you are doing without issues in understanding plus you will have to use less code.

It's no magic or anything... just a pleasant shorthand for anonymous functions.

partial(alert, "FOO!") is equivalent to function(){alert("FOO!");}

partial(Math.max, 0) corresponds to function(x){return Math.max(0, x);}

The calls to partial (MochiKit terminology. I think some other libraries give functions a .curry method which does the same thing) look slightly nicer and less noisy than the anonymous functions.

As for libraries using it, there's always Functional.

When is it useful in JS? Probably the same times it is useful in other modern languages, but the only time I can see myself using it is in conjunction with partial application.

I would say that, most probably, all the animation library in JS are using currying. Rather than having to pass for each call a set of impacted elements and a function, describing how the element should behave, to a higher order function that will ensure all the timing stuff, its generally easier for the customer to release, as public API some function like "slideUp", "fadeIn" that takes only elements as arguments, and that are just some curried function returning the high order function with the default "animation function" built-in.

Here's an example.

I'm instrumenting a bunch of fields with JQuery so I can see what users are up to. The code looks like this:

$('#foo').focus(trackActivity);$('#foo').blur(trackActivity);$('#bar').focus(trackActivity);$('#bar').blur(trackActivity);

(For non-JQuery users, I'm saying that any time a couple of fields get or lose focus, I want the trackActivity() function to be called. I could also use an anonymous function, but I'd have to duplicate it 4 times, so I pulled it out and named it.)

Now it turns out that one of those fields needs to be handled differently. I'd like to be able to pass a parameter in on one of those calls to be passed along to our tracking infrastructure. With currying, I can.

JavaScript functions is called lamda in other functional language. It can be used to compose a new api (more powerful or complext function) to based on another developer's simple input. Curry is just one of the techniques. You can use it to create a simplified api to call a complex api. If you are the develper who use the simplified api (for example you use jQuery to do simple manipulation), you don't need to use curry. But if you want to create the simplified api, curry is your friend. You have to write a javascript framework (like jQuery, mootools) or library, then you can appreciate its power. I wrote a enhanced curry function, at http://blog.semanticsworks.com/2011/03/enhanced-curry-method.html . You don't need to the curry method to do currying, it just help to do currying, but you can always do it manually by writing a function A(){} to return another function B(){}. To make it more interesting, use function B() to return another function C().

I agree that at times you would like to get the ball rolling by creating a pseudo-function that will always have the value of the first argument filled in. Fortunately, I came across a brand new JavaScript library called jPaq (http://jpaq.org/) which provides this functionality. The best thing about the library is the fact that you can download your own build which contains only the code that you will need.

Just wanted to add some resources for Functional.js:

Lecture/conference explaining some applicationshttp://www.youtube.com/watch?v=HAcN3JyQoyY

Updated Functional.js library:https://github.com/loop-recur/FunctionalJSSome nice helpers (sorry new here, no reputation :p):/loop-recur/PreludeJS

I've been using this library a lot recently to reduce the repetition in an js IRC clients helper library. It's great stuff - really helps clean up and simplify code.

In addition, if performance becomes an issue (but this lib is pretty light), it's easy to just rewrite using a native function.

You can use native bind for quick, one line solution

function clampAngle(min, max, angle) {var result, delta;delta = max - min;result = (angle - min) % delta;if (result < 0) {result += delta;}return min + result;};var clamp0To360 = clampAngle.bind(null, 0, 360);console.log(clamp0To360(405)) // 45

Another stab at it, from working with promises.

(Disclaimer: JS noob, coming from the Python world. Even there, currying is not used all that much, but it can come in handy on occasion. So I cribbed the currying function - see links)

First, I am starting with an ajax call. I have some specific processing to do on success, but on failure, I just want to give the user the feedback that calling something resulted in some error. In my actual code, I display the error feedback in a bootstrap panel, but am just using logging here.

I've modified my live url to make this fail.

function ajax_batch(e){var url = $(e.target).data("url");//induce errorurl = "x" + url;var promise_details = $.ajax(url,{headers: { Accept : "application/json" },// accepts : "application/json",beforeSend: function (request) {if (!this.crossDomain) {request.setRequestHeader("X-CSRFToken", csrf_token);}},dataType : "json",type : "POST"});promise_details.then(notify_batch_success, fail_status_specific_to_batch);}

Now, here in order to tell the user that a batch failed, I need to write that info in the error handler, because all it is getting is a response from the server.

I still only have the info available at coding time - in my case I have a number of possible batches, but I don't know which one has failed w.o. parsing the server response about the failed url.

function fail_status_specific_to_batch(d){console.log("bad batch run, dude");console.log("response.status:" + d.status);}

Let's do it. Console output is:

console:

bad batch run, dudeutility.js (line 109)response.status:404

Now, let's change things a bit and use a reusable generic failure handler, but also one that is curried at runtime with both the known-at-code-time calling context and the run-time info available from event.

 ... rest is as before...var target = $(e.target).text();var context = {"user_msg": "bad batch run, dude. you were calling :" + target};var contexted_fail_notification = curry(generic_fail, context); promise_details.then(notify_batch_success, contexted_fail_notification);}function generic_fail(context, d){console.log(context);console.log("response.status:" + d.status);}function curry(fn) {var slice = Array.prototype.slice,stored_args = slice.call(arguments, 1);return function () {var new_args = slice.call(arguments),args = stored_args.concat(new_args);return fn.apply(null, args);};}

console:

Object { user_msg="bad batch run, dude. you were calling :Run ACL now"}utility.js (line 117)response.status:404utility.js (line 118)

More generally, given how widespread callback usage is in JS, currying seems like a quite useful tool to have.

https://javascriptweblog.wordpress.com/2010/04/05/curry-cooking-up-tastier-functions/http://www.drdobbs.com/open-source/currying-and-partial-functions-in-javasc/231001821?pgno=2

I asked a similar question at https://softwareengineering.stackexchange.com/questions/384529/a-real-life-example-of-using-curry-function

But only after I use ramda do I finally appreciate the usefulness of curry. So I will argue that if we need to chain functions together to process some input data one step a time, e.g. the promise chain example in the article Favoring Curry, using curry by "function first，data last", the code does look clean!

Here you have a practical example of were currying is being used at the moment.https://www.joshwcomeau.com/react/demystifying-styled-components/

Basically he is creating a poor man styled components and uses currying to "preload" the name of the tag when creating a new style for it.