-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Rdar 29016063 swift 3.1 branch precompile bridging header #6768
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rdar 29016063 swift 3.1 branch precompile bridging header #6768
Conversation
We're trying to get rid of implicit bridging-header imports, as a feature. These are IMPORTED_HEADER blocks left in modules built with bridging headers, that trigger re-importing the bridging header into any client that imports the module. As a half-way measure to deprecating them, we add a warning here that triggers when an implicit bridging-header import occurs that is _not_ suppressed as redundant by clang.
This happens fairly regularly in unit testing scenarios.
@swift-ci test |
Unfortunately it won't build without its corresponding change in clang: apple/swift-clang#61 |
Which we can do! apple/swift-clang#61 |
Build failed |
…unless update_checkout fails for some reason. @erg? |
Build failed |
apple/swift-clang#61 |
Build failed |
Build failed |
"18:39:57 NameError: global name 'lock' is not defined" uh yes, that's not me! |
Cherry-pick for swift-3.1-branch of #5977
Includes option setting the bridging PCH system to off by default.
See rdar://29016063