👍 (once the build is passing!)

once the build is passing!

That was deedpoll scolding me for using i as an identifier. I was seduced by the prospect of var a, b, c, d, e, f, g, i;. :)

Theres already a name for this which I'm trying to recall

-- Found it see lodash/lodash#756

Also, I've found used a method in the past in my own code, but don't see it being useful enough for inclusion 😐

I like this reversion of apply in the test, so unapply sounds like the correct name

g = R.unapply(R.apply(f)) === f;

Have a feeling this could be used for #484

Are you on board, @buzzdecafe?

I'm +0 for this but it should be called spread to align with ES6

ok by me.

not quite as powerful as ES6 spread, e.g. [1, 2, ...nums, 11, 12], for what that's worth.

"Spreading" is synonymous with R.apply, no?

f(...iterableObj);

The above is roughly equivalent to:

R.apply(f, iterableObj);

In my view "apply" is better name for this function than "spread". From Wikipedia:

Apply is also the name of a special function in many languages, which takes a function and a list, and uses the list as the function's own argument list, as if the function were called with the elements of the list as the arguments.

There's potential for confusion, of course, as JavaScript functions have an apply method which serves almost the same purpose, but in Ramda code one is rarely concerned with this.

I prefer R.apply+R.unapply to R.spread+R.unspread.

ok with the code & docs--thoughts on the name @CrossEye ?

The code is fine... the docs work... either name is definitely better than splat/unsplat. I think our apply is very close to the language's apply; let's keep this inverse named similarly. 👍 for unapply, even if on it's own it makes little sense. (Sounds as though I don't want the job anymore...)

One of you could hit the green button. :)

Is that what the green button is for? I get it! 😈