-
-
Notifications
You must be signed in to change notification settings - Fork 646
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
Nested package statements not inferred for Scala #13655
Comments
@stuhood: Is there a particular example of this? I'm not sure what is meant by "results in symbols in both packages being available". The provided symbols calculated for a file should all be attributed to |
Sorry, clarified the description to indicate that this is about which symbols are available as unqualified within the file, rather than which package declared symbols live in. |
Example of how it should work:
Okay first step will be a PR to analyze the actual package statements. |
#13738 parses out the package scopes. |
As described in #13655, unqualified symbols in Scala code can come from any of the packages for which there is a `package` directive in the source file. The first step to solving this issue is to parse the packages referenced by a Scala file. [ci skip-build-wheels]
This represented roughly 10% of the issues in |
...results in symbols in both packages being available as unqualified within the file.
This is likely because we don't attempt to resolve against all of the nested scopes for a symbol here:
pants/src/python/pants/backend/scala/dependency_inference/scala_parser.py
Lines 132 to 140 in c7cd090
The text was updated successfully, but these errors were encountered: