-
Notifications
You must be signed in to change notification settings - Fork 462
Work around a retroactive conformance bug in Swift 6.2 #3177
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
Work around a retroactive conformance bug in Swift 6.2 #3177
Conversation
dfd4206 to
4baf5fc
Compare
|
@swift-ci please test |
|
@swift-ci please test Windows |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have an issue for that bug? If so, could we add a comment that references it and a comment that says that we can remove this workaround once we no longer support Swift 6.2?
4baf5fc to
61d935e
Compare
Sure, there wasn't an issue but I filed one for tracking purposes and mentioned it by the workarounds. |
The Swift 6.2 compiler emits spurious warnings about retroactive conformances to protocols that are inherited through a protocol that is written module qualified in the inheritance clause (the Swift compiler bug is tracked by swiftlang/swift#85153). Suppress the warnings by making the inherited conformances explicit and module qualified.
61d935e to
8ae4577
Compare
|
@swift-ci please test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
|
@swift-ci Please test |
The Swift 6.2 compiler emits spurious warnings about retroactive conformances to protocols that are inherited through a protocol that is written module qualified in the inheritance clause (the Swift compiler bug is tracked by swiftlang/swift#85153). Suppress the warnings by making the inherited conformances explicit and module qualified.