Skip to content

[SE-0364][chore]: make full-qualification suppression text better match implementation #3010

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −2
Open

[SE-0364][chore]: make full-qualification suppression text better match implementation #3010

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions proposals/0364-retroactive-conformance-warning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,11 +113,11 @@ use `@retroactive` outside of the declaration of a retroactive conformance.
`@retroactive` is a new attribute, but it is purely additive; it can be accepted
by all language versions. It does mean projects building with an older Swift
will not have access to this syntax, so as a source compatible fallback,
a client can silence this warning by fully-qualifying all types in the extension.
a client can silence this warning by fully-qualifying all protocol types in the extension.
As an example, the above conformance can also be written as

```swift
extension Foundation.Date: Swift.Identifiable {
extension Date: Swift.Identifiable {
// ...
}
```
Expand Down