Add support for handling re-exports and visibility #131
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.
A re-export is when an item is imported into a file, like so:
This requires a bit of care, since the import system is orthogonal to the compile meta system. The hope is that they can be merged at some point.
Note: access checking is still only checked once, from where something is used to where it's declared. So we currently don't support access to get around visibility (yet). Uses also aren't cached, but this will happen once the import system is moved into
Query
, instead ofUnitBuilder
where it is now.We do detect cycles at this point. And support wildcards: