[5.9 🍒] Miscellaneous Dependency Scanner and Explicit Modules Improvements #1386
Conversation
This file contains hidden or 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
… separate dependency details field Instead of assuming such dependencies are contained in the 'directDependencies' field of the module info, support querying them from a details of a textual module.
|
@swift-ci test |
Adds support for '-explain-dependency <MODULE_NAME>', which causes the driver to run a dependency scan, and find all dependency paths that cause the main module to depend, directly or transitively, on a given module dependency.
artemcm
force-pushed
the
ExplicitModule59CherrySeason
branch
from
26daecd to
122976b
Compare
|
@swift-ci test |
|
@swift-ci test Windows platform |
nkcsgexi
approved these changes
Jun 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 #1365 and #1363
• Release: Swift 5.9
• Explanation: Cherry-picks of a handful of changes to the dependency scanner, in order to facilitate early experimental adoption of explicit module loading in release compilers. Also cherry-picks the new
-explain-dependencyoption, which is purely an opt-in feature and does not affect existing code paths.• Scope of Issue: This issue impacts only users who opt-in to Explicit Module Builds with the driver's -experimental-explicit-module-build.
• Origination: Development of Explicit Module loading
• Risk: The risk of this change is low, affected code-paths are not triggered during Implicit Module builds (default)
• Reviewed By: @nkcsgexi