Functional JavaScript, Part 3: apply, call, and the arguments object

Re:Functional JavaScript, Part 3: apply, call, and the argum... by thinkpad20 on Tuesday April 22, 2014 @05:18PM (#7630514)

I think your post is a bit misleading; in the OCaml example, both functions are curried. This would be a better juxtaposition (I'm mostly guessing at the syntax; I'm a Haskeller).

    let uncurried = fun (foo, bar, baz) -> qux
    let curried = fun foo bar baz -> qux

It's a relatively small nitpick, but that's what currying means in this instance. And really, JavaScript is the same way; a function with "multiple arguments" is really just a function where the argument is a tuple. It's just that syntactically, it's cleaner in JavaScript (and many other languages) to declare and call functions with tuples.

[ Parent | on HN ]

Re:Functional JavaScript, Part 3: apply, call, and the argum... by lrichardson on Tuesday April 22, 2014 @05:41PM (#7630672)

I guess I didn't mean for it to be misleading, but I wrote the example like I did on purpose to show that in OCaml, the arguments are curried by default... that there is no need to have the `fun` keyword 3 times.

The misleading part was probably naming the first function "uncurried"... the point of the example was to show that they were both curried.

I'll try to make this more clear in my post. Thanks.

[ Parent | on HN ]