Fixes #225, add a section on Scala functions

[ochrons]

No description provided.

[stewSquared]

And line 416 isn't completely true. Currying isn't distinguished as a concept from partial application by multiple parameter lists, although it's true that currying is allowed in scala if you write a function with multiple parameter lists. Perhaps it's best just to give a simple, language-agnostic definition of currying here.

[sjrd]

@stewSquared Thanks for the proofreading. It is easier to process it if you use line comments, though, as then the comments are visually attached to the lines you're commenting on. It would be easier for you, too, as you won't have to report the line numbers into your comment.

[stewSquared]

@sjrd Of course! Thanks for the tip.

[ochrons]

In the Scala documentation currying is defined as

Methods may define multiple parameter lists. When a method is called with a fewer number of parameter lists, then this will yield a function taking the missing parameter lists as its arguments.

Another Scala definition I found was

Currying transforms a function that takes multiple parameters into a chain of functions, each taking a single parameter. Curried functions are defined with multiple parameter lists.

Of course the "purist" view is that curried function has always only a single parameter, but in practice "currying" is used in a more relaxed way in Scala. For our purpose, the point of multiple parameter lists is more important than the "real" currying.

[stewSquared]

Okay, that's a fair point. I'm glad to help out!

[sjrd]

Shouldn't this be a level-3 header (and not 4)?

[ochrons]

The 2 vs 4 level has been used elsewhere, too, for better visual clarity.

[sjrd]

OK let's keep it that way for now, but we should globally fix this another time.

[sjrd]

That's all.

[sjrd]

LGTM