Alternative formulation of orElse and getOrElse #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cc #4
This renames the current
getOrElse
togetOr
and adds a newgetOrElse
that takes a function returning a value. In case it helps, this matches Rust’sOption.unwrap_or_else
and Scala’sOption.getOrElse
. It is, obviously and unfortunately, a breaking change.If this makes sense, I would like to extend the PR to do the same for the current
orElse
, for consistency: it should be renamed toor
, andorElse
should be the version that takes a function returning anOption
.(I also fixed the duplicated
four
th test.)