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
Implicit resolution inconsistency #5354
Comments
Imported From: https://issues.scala-lang.org/browse/SI-5354?orig=1 |
@odersky said: |
@odersky said: The fix is twofold: (1) We make isNonBottomSubClass smarter so that it always returns false if the symbol in question is not a type; hence the info need not be computed. (2) It's dubious to swallow CyclicReference errors anywhere, but I deemed it too risky to propagate them. But at least the CyclicReference is now logged if -Ylog-implicit is true. This hopefully spares future maintainers the same detective work I had to go through when digging this out. Leaving for Paul to close once pull request is accepted. |
@paulp said: |
@retronym said: http://stackoverflow.com/questions/10763511/implicit-resolution-in-scala-2-10-x-whats-going-on 2.9.2 considered |
The following two programs should both give ambiguity errors, but only the first one does:
This one compiles without error, but shouldn't:
The text was updated successfully, but these errors were encountered: