News for hackers. Stuff that matters.
Re:A Case Against Currying by jstrieb on Sunday March 22, 2026 @10:46AM (#47478068)
I like currying because it's fun and cool, but found myself nodding along throughout the whole article. I've taken for granted that declaring and using curried functions with nice associativity (i.e., avoiding lots of parentheses) is as ergonomic as partial application syntax gets, but I'm glad to have that assumption challenged.

The "hole" syntax for partial application with dollar signs is a really creative alternative that seems much nicer. Does anyone know of any languages that actually do it that way? I'd love to try it out and see if it's actually nicer in practice.

Re:A Case Against Currying by emih on Sunday March 22, 2026 @10:58AM (#47478196)
Glad to hear the article did what I meant for it to do :)

And yes, another comment mentioned that Scala supports this syntax!

Re:A Case Against Currying by rocqua on Sunday March 22, 2026 @11:01AM (#47478241)
Someone else in the comments mentioned that scala does this with _ as the placeholder.
Re:A Case Against Currying by runevault on Sunday March 22, 2026 @01:49PM (#47480120)
Clojure CL as well have macros that let you thread results from call to call, but you could argue that's cheating because of how flexible Lisp syntax is.
Re:A Case Against Currying by hencq on Sunday March 22, 2026 @04:00PM (#47481489)
Clojure also has the anonymous function syntax with #(foo a b %) where you essentially get exactly this hole functionality (but with % instead of $). Additionally there’s partial that does partial application, so you could also do (partial foo a b).