Skip to content

Conversation

@SethTisue
Copy link
Member

as per #5135

review by @szeiger, @Ichoran, @soc, community. (this will likely be
merged rapidly, but that doesn't mean additional changes, e.g. to the
Scaladoc, can't follow)

for two reasons:
* to facilitate warning-free cross-compilation between Scala 2.11
  and 2.12
* because it's not clear that .swap is a good replacement for .left

Either.right seems almost certain to be deprecated in 2.13.
Either.left's future is uncertain; see discussion (and links to
additional discussions) at scala#5135
@scala-jenkins scala-jenkins added this to the 2.12.0-RC2 milestone Sep 29, 2016
Copy link
Contributor

@szeiger szeiger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't agree with the premise that source compatibility between two releases implies being able to build without warnings on both, but I'm in no hurry to deprecate these methods.

@SethTisue
Copy link
Member Author

I don't agree with the premise that source compatibility between two releases implies being able to build without warnings on both

noted. in the general case, I agree.

@Ichoran
Copy link
Contributor

Ichoran commented Sep 29, 2016

LGTM

@adriaanm
Copy link
Contributor

I'm going to ignore the spurious test failures and merge this.

@adriaanm adriaanm merged commit 510d8ef into scala:2.12.0 Sep 29, 2016
@SethTisue SethTisue deleted the undeprecate-either-left-right branch September 29, 2016 19:59
@adriaanm adriaanm added the release-notes worth highlighting in next release notes label Oct 15, 2016
@SethTisue
Copy link
Member Author

/nothingtoseehere

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-notes worth highlighting in next release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants