swift_import: always link the import.#1343
Merged
brentleyjones merged 1 commit intomasterfrom Oct 4, 2024
Merged
Conversation
`swift_library` is also moving in this direction. SwiftPM works by linking all the .o files, so this should end up in a state that seem users familiar with SwiftPM/Xcode will expect. Otherwise an `@objc` class might not be findable by name only, or a protocol conformance might not get included leading to confusing runtime problems. PiperOrigin-RevId: 527908878 (cherry picked from commit 2cc542a)
luispadron
approved these changes
Oct 4, 2024
Collaborator
Author
|
Technically this is a breaking change. Adding the label, but I don't know if this alone would be enough for us to bump our version. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
swift_libraryis also moving in this direction.SwiftPM works by linking all the .o files, so this should end up in a state that seem users familiar with SwiftPM/Xcode will expect. Otherwise an
@objcclass might not be findable by name only, or a protocol conformance might not get included leading to confusing runtime problems.PiperOrigin-RevId: 527908878
(cherry picked from commit 2cc542a)