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 visibility.
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 visibility !
Visibility is about what a
class or an
object expose to the rest of the world.
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 (8lBYPLO0RAGZLT1C7idAuw).
More information about Scala visibility
In this exercise you will learn (or have learned, if you have already solved the puzzle) about Scala visibility.
Let’s review the different kind of visibility:
public: In scala, the
publickeyword does not exist, this is the default behavior. If nothing is specified, the member of this context will be available for all to call.
private: This will make the member not visible to the rest of the world (There is an exception about
companion object, we are going to learn about it in a future SKB).
protected: This was not illustrated in this exercise. It is related to object oriented programming and more specifically about inheritance. We are going to learn more about it in a later SKB.
Feel free to go back to the exercise, modify the code to try out new things and get a better intuition for Scala visibility.
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! 🙂