Don't require objc in modulemaps generated for Swift compatibility headers #616
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.
Let's remove the
requires objc
from the module map file generated for the compatibility header. This condition triggered an error when importing the compatibility header from a C source file.The
require objc
isn't necessary, the compatibility header is already printed in a way where the Objective-C code is protected behind a language check. C clients can safely import the current compatibility header even if they may not see any content.Let's lift this restriction. It isn't currently necessary and we're adding C content to the compatibility header with the official support for
@cdecl
that is independent of Objective-C.swiftpm equivalent change: swiftlang/swift-package-manager#8736