News for hackers. Stuff that matters.
Re:What is the advantage of currying? by rwmj on Saturday February 02, 2013 @09:04AM (#5155966)
In a traditionally compiled language, currying doesn't provide varargs: the compiler still has to know how many parameters a function takes before it can be called. You cannot write `printf "%d" 1' expecting that at runtime printf is going to parse the string and read further arguments, because the compiler wouldn't know when printf can be called.

OCaml famously (or notoriously) hacks this knowledge into the compiler, so the compiler knows about format strings and parses them. This is nicely typesafe, but means you cannot use varargs in your own functions, and there are odd restrictions on the format string. (You can use the camlp4 preprocessor, or lists-as-parameters, to get around this).

Re:What is the advantage of currying? by chongli on Saturday February 02, 2013 @11:36AM (#5156411)
Haskell has printf without using lists-as-parameters. It accomplishes this by doing some very clever type-level trickery. The key idea is in the recursive definition of this instance of PrintfType:

    instance (PrintfArg a, PrintfType r) => PrintfType (a -> r) where
Re:What is the advantage of currying? by philsnow on Saturday February 02, 2013 @03:43PM (#5157263)
Your snippet got cut off, care to paste the rest? I'm guessing it works by popping the format string and the first operand off the args, and then finding the first formatting escape in the format string and formatting it, then recurse.
Re:What is the advantage of currying? by chongli on Saturday February 02, 2013 @04:52PM (#5157504)
Yeah, sorry. Here's the full snippet:

    instance (PrintfArg a, PrintfType r) => PrintfType (a -> r) where
    spr fmts args = \ a -> spr fmts (toUPrintf a : args)
And spr is a polymorphic function of the type:

    spr :: String -> [UPrintf] -> t
Essentially the way this works is that it recursively conses up a list of the arguments, calling toUPrintf on each.
Re:What is the advantage of currying? by guard-of-terra on Saturday February 02, 2013 @09:07AM (#5155977)
"the compiler still has to know how many parameters a function takes before it can be called"

I guess it's better viewed as: type system has to figure out whether a consecutive currying/calling will return a scalar/function of zero arguments.