Partial application and currying

[zloirock]

What do you think about something like that:

// partial application without binding `this`, unlike `.bind`
((a, b) ==> a + b).partial(1)(2) // => 3
(function (a, b) { return this + 1 + 2 }).partial(2).call(1, 3) // => 6

// curring
((a, b) ==> a + b + c).curry(1)(2)(3) // => 6

[js-choi]

Unfortunately, I am reluctant to include a currying function in this proposal. Programming styles involving heavy currying have been quite controversial in TC39 (performance concerns, ecosystem-schism concerns, aesthetic concerns, etc.); see tc39/proposal-pipeline-operator#221.

I anticipate that including a Function.curry would reduce the chances of this entire proposal advancing. So I’m going to avoid including anything that TC39 would perceive as benefiting or encouraging currying-heavy styles. I would push curry to another proposal, if this first proposal succeeds.

I’m holding off on Function.partial to avoid stepping on the toes of @rbuckton’s partial-function-application syntax proposal. We could always add Function.partial later. First steps.

It might be would be worth calling this out in the explainer sometime; I’ll close this issue when I add that to the explainer. Anyways, sorry if this isn’t the answer you wanted.