Currying Partial application perhaps?

# random

[karelpeeters]

Currying Partial application perhaps?

[Andreas Sinz]

How would that look like with a fictional syntax?

[ebonet]

http://baddotrobot.com/blog/2013/07/21/curried-functions/ (in Java and Scala)

[karelpeeters]

fun sum(a: Int, b: Int) = a + b and then ::sum(3) is a function reference with a curried. Maybe even allow named parameters...

[Andreas Sinz]

oh, so you are talking about partial application

[karelpeeters]

Currying is related to, but not the same as, partial application.

~Wikipedia

Dammit, you can tell I'm not that into functional programming.

[karelpeeters]

But yes, turns out I was taking about partial application 🙄

[Andreas Sinz]

partial application + named parameters would be very nice fun add(x: Int, y: Int) = x + y; val add5 = ::add(y = 5) 😄

[Andreas Sinz]

@cedric ^ what about that syntax for partial application with support for named parameters?

[karelpeeters]

What does he have to do with this? Did I miss anything?

[Andreas Sinz]

was a discussion a while ago where cedric said he wanted to have support for named parameters with partial application

[Andreas Sinz]

in haskell the function-arguments are ordered the "right" way in order to use partial application, e.g. map takes the function first and the list as second parameter, so you can apply the same function to multiple lists. in java/kotlin world the arguments are ordered how the library author wants it, so that could possibly render some functions being bad candidates for partial applications if you need to apply the second/third/whatever argument