We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
object X def f(e: Either[Int, X.type]) = e match { case Left(i) => i case Right(X) => 0 }
gives:
warning: match may not be exhaustive. It would fail on the following input: Right(<not X>)
Is this correct? Surely the match is in fact exhaustive.
(c.f. http://stackoverflow.com/questions/11166098/why-does-scala-2-10-give-match-may-not-be-exhaustive-warning-when-matching-on, where it was suggested I post this as a bug report.)
The text was updated successfully, but these errors were encountered:
Imported From: https://issues.scala-lang.org/browse/SI-5968?orig=1 Reporter: Scott Morrison (scott) Affected Versions: 2.10.0-M4 Other Milestones: 2.10.0
Sorry, something went wrong.
@retronym said: This seems to do the trick: https://github.com/retronym/scala/compare/ticket/5968
@adriaanm said: Awesome, thanks Jason! Could you please submit a pullreq?
@retronym said: scala/scala@1ef679
retronym
No branches or pull requests
gives:
Is this correct? Surely the match is in fact exhaustive.
(c.f. http://stackoverflow.com/questions/11166098/why-does-scala-2-10-give-match-may-not-be-exhaustive-warning-when-matching-on, where it was suggested I post this as a bug report.)
The text was updated successfully, but these errors were encountered: