Don't check import selectors for Java code #15617
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Moving import selector checking from PostTyper to Typer had the side-effect that they were also checked in Java code. But that does not work since the Java files are compiled before the Scala files so the selected reference has not been seen yet. Fixed by disabling import selector checks for Java files. Fixes scala#15608
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Moving import selector checking from PostTyper to Typer had the
side-effect that they were also checked in Java code. But that does
not work since the Java files are compiled before the Scala files
so the selected reference has not been seen yet.
Fixed by disabling import selector checks for Java files.
Fixes #15608