Back on partial application. Currying makes a lot...
# language-proposals
Back on partial application. Currying makes a lot of sense when used with various high-order functions. Like, for example, various kinds of pipeline operators (and that's where most of it's usages actually belong). This, indeed, imposes some coding style, which affects library design. Now, in Kotlin function pipeline is usually written as a sequence of calls with receiver. And, of cause, it also affects how libraries are designed. These two are kinda dual. My Scala-fu is somewhat dusty, but in F# there's a problem: methods (functions with receivers) don't play well with currying. So yeah, in a brave new functional world you'll see a lot of currying. In mostly OO codebases - not quite much.