[6.2 🍒][Dependency Scanning] Keep track of each imported module's access control #82779
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.
Cherry-pick of #82169
Explanation: Adds an access control field for each imported module identified. When multiple imports of the same module are found, this keeps track of the most "open" access specifier.
Scope: Builds which enable Explicitly built modules.
Risk: Low. These changes are largely additive to the dependency scanner and are not currently relied upon by build system clients.
Reviewed By: @xymus
Problem: rdar://148055487
Original PR: [Dependency Scanning] Keep track of each imported module's access control #82169