[6.2 🍒][Explicit Module Builds] Adopt new direct-import field for Swift source modules #1886
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 #1877
Explanation:Adopts new Swift dependency scanner API to query only directly-imported module dependencies for the module being scanned. This API, for the main source module, provides info on which dependencies are directly imported into the user program, explicitly ('import' statement) or implicitly (e.g. stdlib). This list does not include Swift overlay dependencies, cross-import dependencies, bridging header dependencies.
Scope: Does not affect existing clients, provides a new API.
Risk: Low, this is a purely additive API change which should not affect existing clients.
Testing: Added a test to the driver test suite.
Issue: rdar://146697570