These are chat archives for ramda/ramda
R.anyPass(arr1.map(val => R.equals(val)))?
t[n].apply is not a function
Array.prototype.mappasses more than one argument to the fn.
passes more than one value to the fn.
why in the world would a function do that? (just kidding!)
equals( x, y )equivalent to
equals( x )( y ), instead requiring one argument per invocation (i.e. the second syntax).
I've been thinking about what changes might go in a Ramda 2.0 if we ever get Ramda 1.0 out the door, and one of the best simplifications I can imagine is to drop all support for polyadic functions. This of course would make it more Haskell-like, and I think would gel well with this Sanctuary proposal.
tap( console.log )( undefined ) // Cannot read property '@@transducer/step' of undefined
tapbug would have been introduced
undefinedbut I saw the error instead.
undefinedbefore checking for a property on it. I'll file an issue and work on a PR.