-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Diagnostics] Add new groups to the 'deprecated' diagnostic group #76454
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
[Diagnostics] Add new groups to the 'deprecated' diagnostic group #76454
Conversation
@@ -1,10 +1,7 @@ | |||
// RUN: not %target-swift-frontend -typecheck -diagnostic-style llvm -warnings-as-errors %s 2>&1 | %FileCheck %s --check-prefix=CHECK-WAE | |||
// RUN: not %target-swift-frontend -typecheck -diagnostic-style llvm -Werror availability_deprecated %s 2>&1 | %FileCheck %s --check-prefix=CHECK-WE-GROUP | |||
// RUN: not %target-swift-frontend -typecheck -diagnostic-style llvm -Werror deprecated %s 2>&1 | %FileCheck %s --check-prefix=CHECK-WE-SUPERGROUP |
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.
I'm removing -SUPERGROUP
tests here because we don't currently have any. I'll bring it back in a future PR (probably with the Concurrency
supergroup).
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.
Yeah, that's fine.
e02d7e1
to
aa5e10f
Compare
@DougGregor Can you take a look and run tests, please? |
@swift-ci please smoke test Linux |
@AnthonyLatsis Can you run the other tests as well? |
@swift-ci please smoke test Windows |
@swift-ci please smoke test macOS |
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.
This looks great. I might quibble with the removal of the Deprecated supergroup, but it shouldn't prevent this PR from landing.
@@ -1,10 +1,7 @@ | |||
// RUN: not %target-swift-frontend -typecheck -diagnostic-style llvm -warnings-as-errors %s 2>&1 | %FileCheck %s --check-prefix=CHECK-WAE | |||
// RUN: not %target-swift-frontend -typecheck -diagnostic-style llvm -Werror availability_deprecated %s 2>&1 | %FileCheck %s --check-prefix=CHECK-WE-GROUP | |||
// RUN: not %target-swift-frontend -typecheck -diagnostic-style llvm -Werror deprecated %s 2>&1 | %FileCheck %s --check-prefix=CHECK-WE-SUPERGROUP |
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.
Yeah, that's fine.
Yeah, I'm not sure about the removal as well but some folks have raised a discussion about whether we should group the language-level deprecations with sources-level deprecations. I feel like it wouldn't be a problem but this discussion may take a while, and I want to land the minimal production-ready support for the feature before 6.1 is branched (so we have at least something usable). |
I am 100% on board with this approach. |
@DougGregor Can you merge this, please? |
Yes, done! |
https://forums.swift.org/t/diagnostic-groups-deprecated/74581
This change
Removes:
Renames:
DeprecatedDeclaration
(conformance_deprecated and witness_deprecated and "deprecated protocol conformance" are in this group as well)