Skip to content

Fix #8396: Make prefixes of abstract types contribute to implicit scope #8410

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 1 commit into from
Mar 4, 2020

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Mar 1, 2020

The comment already said the right thing -- abstract types are anchors --
but the implementation did not follow it.

…t scope

The comment already said the right thing -- abstract types are anchors --
but the implementation did not follow it.
@odersky
Copy link
Contributor Author

odersky commented Mar 1, 2020

@nicolasstucki The quotedPatterns-4 test moved from neg to pos. I checked that it indeed finds an implicit now which presumably needed to be imported before.

Can you check that the test behaves as expected now, and maybe replace the neg test with another one that still produces the error message?

@nicolasstucki
Copy link
Contributor

quotedPatterns-4 is behaving as expected. This is a huge improvement over a constant source of annoying bugs due to a missing given import. I was considering using opaque types just to not have this issue, which won't be needed anymore.

I don't see an equivalent test neg test to replace it.

@nicolasstucki nicolasstucki merged commit 0f09be3 into scala:master Mar 4, 2020
@nicolasstucki nicolasstucki deleted the fix-#8396 branch March 4, 2020 17:21
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