It's a way to make function interfaces uniform, so that a function becomes a transform from one input value to one output value.
Code example please?
const add = a => b => a + b; const eq = a => b => a === b; eq(5)(add(2)(3));
Just wondering how is that better than this?
const add(a,b)=>a+b; add(2,3);
The decomposition of earlier example reveals a simpler understanding until one understands compositional parameter injection.
It's better if you want to use functions which have a uniform interface of transforming a single input value to a single output value.
Consider using map like so
[1, 2, 3].map(add(3))
Using the binary form of add you would need to introduce an ad hoc function to rectify the interface
[1, 2, 3.map(v => add(3, v))
The one to one mapping style generally makes composition simpler.
So, the question is, do you want to do that kind of stuff?
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It's a way to make function interfaces uniform, so that a function becomes a transform from one input value to one output value.
Code example please?
Just wondering how is that better than this?
The decomposition of earlier example reveals a simpler understanding until one understands compositional parameter injection.
It's better if you want to use functions which have a uniform interface of transforming a single input value to a single output value.
Consider using map like so
[1, 2, 3].map(add(3))
Using the binary form of add you would need to introduce an ad hoc function to rectify the interface
[1, 2, 3.map(v => add(3, v))
The one to one mapping style generally makes composition simpler.
So, the question is, do you want to do that kind of stuff?