News for hackers. Stuff that matters.
Re:Currying in JavaScript by renke1 on Sunday September 19, 2021 @06:44AM (#28583261)
The partial application proposal looks reasonable and intuitive. Definitely something I would use. Is there any prior art (other languages etc.)?

Mh, it's already 4 years old. What a shame.

Re:Currying in JavaScript by graftak on Sunday September 19, 2021 @06:55AM (#28583321)
There’s a lot of bikeschedding on how to use it in conjunction with the (also stage 1 proposal and forever delayed) pipeline operator[1] unfortunately. Add in never ending arguments on which symbol we should use (the questionmark has a lot of responsibilities already) and here we are.

To make matters worse it appear that generally OOP style darlings such as static class blocks and true private fields seem to gain more momentum.

[1] https://github.com/tc39/proposal-pipeline-operator/wiki

Re:Currying in JavaScript by alexfoxgill on Sunday September 19, 2021 @06:48AM (#28583285)
Re:Currying in JavaScript by masklinn on Sunday September 19, 2021 @02:58PM (#28586916)
Clojure has the "thread-as" macro (`as->`), but I don't think it's used much: usually thread-first (`->`) and thread-last (`->>`) will more than do the job and have less mental overhead due to their regularity.
Re:Currying in JavaScript by weego on Sunday September 19, 2021 @06:47AM (#28583277)
Scala has partially applied functions that use a very similar idiom