Clarify the purpose of getOrElse

emma-burrows · web-flow · commit 9c5f115fb167 · 2018-05-31T21:09:00.000+01:00
diff --git a/src/main/scala/stdlib/Options.scala b/src/main/scala/stdlib/Options.scala
@@ -35,7 +35,7 @@ object Options extends FlatSpec with Matchers with org.scalaexercises.definition
    * }
    * }}}
    *
-   * Using `getOrElse` we can provide a default value ("No value") when the optional argument (`None`) does not exist:
+   * Using `getOrElse`, we can extract the value if the `Option[A]` is a `Some[A]`, and provide a default value ("No value") when the optional argument (`None`) does not exist:
    */
   def getOrElseOptions(res0: String, res1: String, res2: String) {
     val value1 = maybeItWillReturnSomething(true)

Original file line number	Diff line number	Diff line change
`@@ -35,7 +35,7 @@ object Options extends FlatSpec with Matchers with org.scalaexercises.definition`
`35`	`35`	`* }`
`36`	`36`	`* }}}`
`37`	`37`	`*`
`38`		- * Using `getOrElse` we can provide a default value ("No value") when the optional argument (`None`) does not exist:
	`38`	+ * Using `getOrElse`, we can extract the value if the `Option[A]` is a `Some[A]`, and provide a default value ("No value") when the optional argument (`None`) does not exist:
`39`	`39`	`*/`
`40`	`40`	`def getOrElseOptions(res0: String, res1: String, res2: String) {`
`41`	`41`	`val value1 = maybeItWillReturnSomething(true)`