[Explicit Module Build] Do not serialize binary .swiftmodule dependencies when building explicit interface dependencies #72499
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
|
@swift-ci test |
tshortli
approved these changes
Mar 21, 2024
…cies when building explicit interface dependencies The build-system (swift-driver) is then responsible for validating all inputs to each module and re-scheduling affected modules.
artemcm
force-pushed
the
NoStatOnSDKDepsSerialization
branch
from
8c6307c to
a38071e
Compare
artemcm
changed the title
stat SDK-relative dependencies when collecting serialization deps
|
@swift-ci test |
xymus
approved these changes
Mar 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
No description provided.