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

Jump to bottom

2.12.x no longer needs future-tense #2211

Merged
merged 1 commit into from
Mar 23, 2018
Merged

2.12.x no longer needs future-tense #2211

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 docs/src/main/tut/datatypes/either.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ e2.right.map(_ + 1)
Note the return types are themselves back to `Either`, so if we want to make more calls to
`flatMap` or `map` then we again must call `right` or `left`.

However, the convention is almost always to right-bias `Either`. Indeed in Scala 2.12.x `Either` will be
However, the convention is almost always to right-bias `Either`. Indeed in Scala 2.12.x `Either` is
[right-biased](https://github.com/scala/scala/pull/5135) by default.

More often than not we want to just bias towards one side and call it a day - by convention,
Expand Down