Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify the purpose of getOrElse #104

Merged
merged 2 commits into from
Jun 8, 2018
Merged

Clarify the purpose of getOrElse #104

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9c5f115
Clarify the purpose of getOrElse
emma-burrows May 31, 2018
c068be1
Split the `getOrElse` explanation into two sentences for clarity.
Jun 7, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/main/scala/stdlib/Options.scala
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 it exists, or return a provided default value. If we have a `Some(x)` we return `x`, and for `None` we return the default value.
*/
def getOrElseOptions(res0: String, res1: String, res2: String) {
val value1 = maybeItWillReturnSomething(true)
Expand Down