Skip to content

Do not choose implicits that are ambiguous references #1141

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

Closed
wants to merge 1 commit into from

Conversation

smarter
Copy link
Member

@smarter smarter commented Mar 3, 2016

Before this commit, implicit_ambiguous_ref.scala failed to compile
because the implict search returned x, we now always try to typecheck
a reference to an identifier before returning it from the implicit search.

Before this commit, implicit_ambiguous_ref.scala failed to compile
because the implict search returned `x`, we now always try to typecheck
a reference to an identifier before returning it from the implicit search.
@smarter smarter force-pushed the fix/implicit_amb_refs branch from ec52017 to 8f34919 Compare March 3, 2016 21:03
@smarter
Copy link
Member Author

smarter commented Mar 3, 2016

/rebuild

1 similar comment
@smarter
Copy link
Member Author

smarter commented Mar 3, 2016

/rebuild

@DarkDimius
Copy link
Contributor

both partests failed. Does not look like false failure to me:

[error] Test dotc.tests.compileMixed failed: java.lang.AssertionError: assertion failed: Wrong # of errors. Expected: 0, found: 29, took 1.174 sec

@smarter
Copy link
Member Author

smarter commented Mar 3, 2016

Oh, I missed those, the failures I saw were due to download failures.

@smarter
Copy link
Member Author

smarter commented Mar 3, 2016

Closing since this was the wrong approach and #1142 needs to be take care of first.

@smarter smarter closed this Mar 3, 2016
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