These are chat archives for ramda/ramda
npm install) you should just be able to build the docs through
npm run docs, which delegates much to the Gruntfile, so you can see the details in there.
f(a)(b)(c)) rather than n (in line with
f(a, b, c))?
curry(f)should return a unary function.
curry, though, so that you don't have to call
curry(f)(a, b, c)or
curry(f)(a, b)(c)is more convenient.
curry(f)(a, b, c)as sugar for
curry(f)(a)(b)(c)or the other way around.
@CrossEye My purpose was to see if someone found these ideas relevant enough to
similar to what Slobodan Blazeski
did in lisp (but with js instead). (Maybe it's even not possible to do so)
In particular, using ramda daily (thx to you all), we ended up centralizing
"axiomatic data" (data that have to be given) into arrays then
projecting/transforming the pieces that we wanted where we wanted using ramda
based point free style functions, instead of having "axiomatic data" spread all
over the place and verbose definitions. I thought that the "dicing" (slicing
sub tables in tables) part of multi-dimensional arrays could be enhanced by
ideas coming from J...
At that point, since something like this has not been done so far, I'll try to
do this and if ever something interesting comes out of this, will share it with
who is interested.
Thx for you time!