This article is part of the Scala knowledge bits Series.
Periodically, I will publish new exercises so you can slowly build up knowledge about Scala.
It is designed to be done in a very short amount of time and learn a little bit each day, just to create a routine.
This episode will teach you about Scala Tuple.
Hope you are going to enjoy it! It is designed for anyone to learn Scala from scratch and slowly learn, one Bit at a time.
After this Bit, I would love to hear your feedback in the comments down below.
Feel free to join the Discord server as well if you would like some help and support from the rest of our community.
What are we learning today?
Today we are going to learn about Scala Tuple !
Imagine, for instance, you would like to pair together an identification number (
) and a name (
Let’s see how to do that in Scala.
Time to try on the exercise on your own and scroll down for more information when you are done or if you are stuck.
Here is an exercise to complete today.
If I did my job well, you should be able to guess by yourself the solution based on what you previously learned and based on the clues.
But if you get stuck, scroll down to get more information.
The goal of the exercise is to replace the
by a piece of code so that the exercise compiles and that’s how you win! Good luck!
You can fill the exercise right in here:
Or, if it does not load, go on to Scastie (TUuvqIPHTc2A3jHNSYMBBQ).
More information about Scala Tuple
In this exercise you will learn (or have learned, if you have already solved the puzzle) about Scala Tuple.
By now, you probably have understood that a Tuple is a way to combine two or more types into one. For instance you can combine a
into a tuple
. You can combine up to 22 Types ! ( You can read more why on here )
The other important aspect is the accessors. For instance, if you have a Tuple
(Double, Int, String)
, to access the first element you have to use
, the second with
Tuples are also involved in the concept of pattern matching that we are going to learn more about later.
As a note about good practices: whenever possible, you should use a
rather than a Tuple. In the long run, it makes things much easier to manage and maintain.
Feel free to go back to the exercise, modify the code to try out new things and get a better intuition for Scala Tuple.
I hope you have learned something new or had fun during this Scala Knowledge Bit.
Please ask questions or post feedback in the comments below.
Feel free to try on the next Scala Knowledege Bit.
If you are curious about the previous Scala knowledge Bits, go check it out! 🙂