These are chat archives for ramda/ramda
TypeError: undefined is not a function
var mapIndexed = R.addIndex(R.map); ^
forEachis a bit of a red-headed stepchild, since it is for side effects. That said, since we do include it, we probably should dispatch on it
Is this a decent way to go about a
let mapThenFlatten = R.curry(R.compose(R.flatten, R.map))
I had to R.curry because it was returning an array and not a function.
chainis known is some languages/libraries as
R.intoyou mentioned there.
R.ofis there mostly to satisfy FantasyLand specification, and it tries to do something useful for lists, but I don't know that we can make it beautiful.
require('../someMainFunc'). Feels like crossing the streams. But somehow, I suspect we already do so, somewhere.
curry(f)()for some positive arity
f. I wanted it to behave like it does now, and return the equivalent of
curry(f). @buzzdecafe argued for throwing an error, because calling it like that is just stupid. We did it that way for some time. But when @davidchambers was trying to make the placeholders more universal, this got turned back to the way I preferred, as it matched a simpler-to-state, and simpler-to-enforce law. I believe @buzzdecafe is playing around with a fork that changes a lot of this, and tries to simplify some of this substantially.
Setimplementation is not it. Would you be willing to write a quick comment on the issue, and people can see if they have another approach that might help?
Justtest, but it's worth discussing.