Hello again! Nice to see you decided to come back. If you check my previous post you know that functions are quite an important matter in the Scala language.
Last time, talking about recursion, I wasn’t able to cover all the topics about functions. So I decided to dedicate yet another post to it. You can call it “advanced functions”, but I don’t think is so “advance” what I’m going to show here.
You are welcome to read some more on functions in this new blog post.
Following the Python Tutorial, I’ll talk a little about this.
Default argument values in Scala are very similar to Python’s. With the difference being in the static types, that is, you’ll have to explicit declare the type of the argument:
As you can see, there is no problem in how to send the arguments, but if you don’t explicitly tell what parameter you are passing, it will use the order to define the assignments.
In Scala you don’t even have to declare all the parameters with default arguments at the end (like in Python), but it’s a good practice as otherwise you’ll face with problems:
You see? In this version of foo, you have to explicit declare z as a passed parameter, otherwise you get an error. That’s why it’s good practice to keep all arguments with default values in the end.
Of course, as parameters have a type, you have to give the a default value of that type (or with an implicit conversion to that type), otherwise is an error:
Now, on the last code I introduce a new value I don’t think I talked about it before: null. The value null is similar to the value None in Python. It’s specially useful to use it on a variable of a particular class when you don’t want to instantiate that class just yet (for example a class defined by you). You can use on some variables of Scala types such as String or List, but not in a primitive type (Int, Double, Char, etc.). We’ll talk more about it when we start working on classes. For now I just wanted to make a quick warning: do not use the (also) reserved word in Scala of None as the value null. It’s not the same, None is a value of a special Scala type called Option, that we’ll discuss in further posts.
Do not use the (also) reserved word in Scala of
Noneas the value
In Scala, as in Python, you can pass an argument representing an arbitrary list of arguments. This argument always has to be defined as the last one and is treated as a list of elements of the defined type (you cannot have a list of types of mixed values):
Now, Scala does not have an equivalent to Python’s **kwargs. There are some workarounds you can do, but I don’t think it’s useful for me to get deep into that.
Lambda expressions (a.k.a. anonymous functions)
Well, anonymous functions, such a powerful and useful tool in Scala (when you start with them, you end up using them everywhere). Anonymous functions are the tool that makes a functional programming language. These are core concept in the paradigm, so obviously I won’t be able to explain it well enough. Instead, I’ll take the example in the Python tutorial, and show how it is done in Scala. Then again, you’ll have to learn more on anonymous functions on your own, as it’s not the idea of my tutorial to teach more than the basics that helps a Python programmer enter in the Scala world.
Anonymous functions are the tool that makes a functional programming language.
Let’s show you the Python example of use of a lambda expression, they create a function which returns a function:
Now, in this example, you create a lambda expression using the lambda reserved word. In Scala the code is quite similar, but you don’t need an extra expression:
Pay attention to the returned value by the function
=> x + n. This is the definition of an anonymous function, basically a function
with it’s parameters, no name and a => operator instead of a = operator.
This functions can have as many parameters as you want and you can directly apply them without making necessary to assign them to a value or variable:
Now, of course, as everything in Scala, functions have types, and sometimes you may need to explicit declare a function type. This can happen, for example, if you are declaring a recursive function with a return value of an anonymous function; however, the function type declaration is fundamental when having a function’s parameter taking a function. This is called higher-order programming and is a topic for another post (a whole post in fact), it’s another of the core features of functional programming.
For now, you only need to now that the type of a function is defined by the type of its parameters and the returning type:
As you see, sometimes the parentheses are not mandatory when the function only takes one parameter but it is obligatory in any other case.
Of course, this examples are very simple and don’t really show the power of anonymous functions nor even why sometimes is necessary to explicit the type. This, hopefully, will come later and you’ll understand the importance of it in a functional programming language like Scala.
So, I think is now time to finish this post. As always, I’ll be thankful on your comments. Best regards and until the next part!