These are chat archives for ramda/ramda

25th
Apr 2015
Hardy Jones
@joneshf
Apr 25 2015 03:55
@buzzdecafe nice!
I still think you should go talk about it during the kanren hangouts
Hardy Jones
@joneshf
Apr 25 2015 04:03
can't seem to install it from npm though
Hardy Jones
@joneshf
Apr 25 2015 04:31
Shouldn't this be:
return new Stream(this.head, this.tail.concat(ys));
also this:
return g(this.head).concat(this.tail.chain(g));
Raine Virta
@raine
Apr 25 2015 11:36
i wonder why javascript doesn't provide syntax for bind when the reality is that how you call a function determines the context in that function
by the same token, perhaps library authors should not assume people are always going to call the exposed functions via some object
grumpyOldRussian
@alexeygolev
Apr 25 2015 13:10
hey guys, anybody uses ramda with immutable.js?
Raine Virta
@raine
Apr 25 2015 15:55
treis now works in browser (w/ browserify) and reads function name and arguments via toString which works nicely some of the time
Asaf
@asaf-romano
Apr 25 2015 17:42
hey all. Am i right that R.compose does NOT return a curried function?
ok, found ramda/ramda#736
Michael Hurley
@buzzdecafe
Apr 25 2015 18:44
@asaf-romano it should IMO. that one is still a sore spot
Raine Virta
@raine
Apr 25 2015 18:54
maybe compose docs could use a brief description how it behaves in different cases
Jethro Larson
@jethrolarson
Apr 25 2015 20:43
I've been experimenting with different ways of calling functions and fn.bind performs bad in pretty much all of them. Also, anything that touches the arguments object performs way worse (apply).
Jethro Larson
@jethrolarson
Apr 25 2015 20:50
When optimizing performance of code using ramda it might be worthwhile to try replacing the variable arity functions with fixed ones.