[Serialization] Drop extensions whose base type can't be deserialized. #11323
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.
This shows up with
swift_wrapper
typedefs, which get imported into Swift as structs. If someone makes an extension of aswift_wrapper
type, but theswift_wrapper
is only applied in Swift 4 mode, that extension will break any Swift 3 clients. Recover by just dropping the extension entirely.There's still more complexity around extensions—what if a requirement can't be deserialized? what if something's depending on the protocol conformance provided by the extension?—but the missing base type case should be pretty safe. If you can't see the type at all, things that depend on its conformances are already in trouble.
rdar://problem/33636733