Skip to content

Fix ambiguity errors with polymorphic implicits #963

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

Merged
merged 2 commits into from
Nov 18, 2015

Conversation

smarter
Copy link
Member

@smarter smarter commented Nov 17, 2015

Previously, isAsSpecific(alt1, tp1, alt2, tp2) did not handle
having tp2 be a polymorphic non-method type like [A]Foo[A].

Also update the documentation of isAsSpecific to account for this
change, the new documentation is based on SLS § 6.26.3 but
adapted to reflect the code.

Review by @odersky

@smarter smarter force-pushed the fix/poly-implicits branch 4 times, most recently from f82d840 to 64a577a Compare November 18, 2015 02:31
Previously, `isAsSpecific(alt1, tp1, alt2, tp2)` did not handle
having `tp2` be a polymorphic non-method type like `[A]Foo[A]`.

Also update the documentation of `isAsSpecific` to account for this
change, the new documentation is based on SLS § 6.26.3 but
adapted to reflect the code.
Also reorder the cases to be in the same order as the documentation.
smarter added a commit that referenced this pull request Nov 18, 2015
Fix ambiguity errors with polymorphic implicits
@smarter smarter merged commit ea1373b into scala:master Nov 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants