buzzdecafe
buzzdecafe
bumping this PR since i could really use this feature. please lmk if there is any way i can help.
@sideshowcoder After rebasing master onto that branch I am getting 71/73 test failures. :smile: Looks like there have been some API changes since this PR. So no, it doesn't work...
could be interesting, are you willing to do a PR? A couple of notes: I think the signature would have to be `Set a -> Set a -> Boolean`; and...
I don't like using arbitrary lists as arguments to a function called `isSubSet`. ``` js const set = [2, 1, 3, 1, 3]; // Not a Set const subset =...
i am disappointed that they do not all crash; that would strike me as the best consistent behavior
> Why the best behaviour is when Ramda raises an exception? because these are all type errors. papering over that fact by requiring special handling for certain values will not...
been down this road before. Under this proposal `gte(5)(6) !== gte(5, 6)`. that is surprising. this is where the placeholders came from, the desire to right-section the non-commutative infix operators.
> I'm in favour of swapping the order of the arguments. Does this argument order hold for any non-commutative infix operator converted to prefix? ``` js gt(5, 10) === true...
> How about providing flipped versions we had that for a while. dropped in favor of placeholder e,g. `var greaterThan5 = R.gt(R.__, 5)` I'd be happy to see those come...
> _It probably means that the function is flipped but could really be anything and you'll need to figure out exactly what by reading the docs._ :laughing: