-
-
Notifications
You must be signed in to change notification settings - Fork 648
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
[internal] scala: parse and report package scopes #13738
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm: we already have the relevant scopes via
consumed_symbols_by_scope
, don't we? In particular, to resolve #13655, it seems like we want to look up a symbol in any of its enclosing scopes, which actually requires the structure that we already have there. See the TODO I linked.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't. The scope key in
consumed_symbols_by_scope
is the scope where the consumed symbol was used, not the scopes that could potentially provide the symbol.Moreover, take this example:
If the file has no consumed symbols in
foo
, thenfoo
won't show up as a scope key inconsumed_symbols_by_scope
even thoughfoo
should be inferred as a scope from which to find consumed symbols.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But the symbol could only possibly be provided by one of the parent scopes, right? Where a symbol is consumed is relevant.
For example, in:
...
class A
should not be visible toclass C
.So is the idea just to walk upward from
consumed_symbols_by_scope
in thescopes
, and suffix the symbol on each parent scope? In future, it might make things easier to include the consuming code in the same change, as it would answer these questions directly.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. In this example, let's say that
class A
referencesX
. Then that symbol could bea.b.X
ora.X
.Also, I'm not understanding why you mentioned "... class A should not be visible to class C." Am I missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I meant: should not be in scope. i.e.,
C
would not be able to refer toA
without qualification. It would need to refer to it as absolute:a.b.A
. So: visible, but not automatically in scope.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rethinking this, that is probably what I'll end up doing. Will handle that in the PR to actually update the dep inference logic.