[Explicit Module Builds] Switch over to loading Clang modules eagerly instead of lazily #72471
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 |
1 similar comment
artemcm
force-pushed
the
EagerExplicitModuleLoading
branch
from
f897a39 to
4df26c7
Compare
artemcm
force-pushed
the
EagerExplicitModuleLoading
branch
from
4df26c7 to
10bc841
Compare
…loading Clang modules eagerly instead of lazily Swift import resolution already does an equivalent to eager module loading during its import resolution phase.
artemcm
force-pushed
the
EagerExplicitModuleLoading
branch
from
10bc841 to
0585ca7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.