IOS-10545 Fix warnings in XCode 16 #400
Merged
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.
ποΈ Jira ticket
https://jira.tid.es/browse/IOS-10545
π₯ What's the goal?
With the release of XCode 16 and Swift 6, new warnings have emerged that can be fixed along with old ones.
π§ How do we do it?
The following changes have been made:
https://github.com/swiftlang/swift-evolution/blob/main/proposals/0364-retroactive-conformance-warning.md
The solution* is backward-compatible with previous versions of XCode by fully-qualifying all types in the extension. As an example, the above conformance can also be written as
* Another solution that we could perhaps consider in the future would be to wrap the modules that we want to conform those types to avoid doing it in the native modules.