There are a lot of ways to deal with the Option
type. First of all, however, do realize how much better it is to have this instead of a potential null
reference! Don't try to get rid of it simply because you are used to how Java works.
As someone else recently stated: stick with it for a few weeks and you will moan each time you have to get back to a language which doesn't offer Option
types.
Now as for your question, the simplest and riskiest way is this:
mymap.get(something).get
Calling .get
on a Some
object retrieves the object inside. It does, however, give you a runtime exception if you had a None
instead (for example, if the key was not in your map).
A much cleaner way is to use Option.foreach
or Option.map
like this:
scala> val map = Map(1 -> 2)
map: scala.collection.immutable.Map[Int,Int] = Map(1 -> 2)
scala> map.get(1).foreach( i => println("Got: " + i))
Got: 2
scala> map.get(2).foreach( i => println("Got: " + i))
scala>
As you can see, this allows you to execute a statement if and only if you have an actual value. If the Option
is None
instead, nothing will happen.
Finally, it is also popular to use pattern matching on Option
types like this:
scala> map.get(1) match {
| case Some(i) => println("Got something")
| case None => println("Got nothing")
| }
Got something
Option
is that it forces you to handle theNone
case. – Niigata