[5.9][ASTGen] Avoid including C standard libary headers in bridging headers #65128
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 #65120 into
release/5.9
Explanation: C stdlib headers are part of
Darwin
/Glibc
clang module. If a Swift file imports a bridging header and that has#include
C stdlib headers, Swift compiler implicitly importsDarwin
/Glibc
overlay modules. That violates dependency layering. I.e. Compiler depends on Darwin overlay, Darwin overlay is created by the compiler. Instead, use builtin types. e.g.size_t
->unsigned long
Scope: Macro expansion related components including
swift-plugin-server
Risk: Low.
Testing: Current regression test suite
Issue: rdar://107957117
Reviewers: Ben Barham (@bnbarham)