-
Notifications
You must be signed in to change notification settings - Fork 337
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.
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
Either.value with some updates #1895
Conversation
* `Either.value` is right biased * Allows users of Scala 2.13 to use `EitherValues` for `Right`s without getting deprecation warnings Also correct param documentation for `Left` and `Right` conversions
…atest into brendanmaguire-either.value
and deprecated the .right.value syntax.
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Bill Venners.
|
@cheeseng can you check this with MIMA? Also I'd like to question the SerialVersionIds. Should we have those or would it be better to leave them off. For the time being I didn't add one for the new class I added (which I'm hoping won't break binary compatibility). |
@bvenners I ran this through MIMA test, for scala 2.10 and 2.11 it fails with:
which I think should be fine, do you concur? I'll submit a PR to ignore that error against your branch. |
* | ||
* @param either the <code>Either</code> on which to add the <code>value</code> method | ||
*/ | ||
implicit def convertEitherToValuable[L, R](either: Either[L, R])(implicit pos: source.Position): Valuable[L, R] = new Valuable(either, pos) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not to use implicit class instead of implicit conversion?
No description provided.