Skip to content

[6.0][Sema] Diagnose deprecated default implementations in the witness checker. #74276

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

Merged

Conversation

hborla
Copy link
Member

@hborla hborla commented Jun 11, 2024

  • Explanation: If a protocol provides a deprecated default implementation for a requirement that is not deprecated, the compiler should emit a warning so the programmer can provide an explicit implementation of the requirement. This is helpful for staging in new protocol requirements that should be implemented in conforming types.
  • Scope: Only impacts protocols that provide deprecated default implementations for non-deprecated requirements, and conforming types that use the default implementation.
  • Issue: rdar://123403268
  • Risk: Low; this change only adds deprecation warnings.
  • Testing: Added a new test.
  • Reviewer: @slavapestov @tshortli @AnthonyLatsis
  • Main branch PR: [Sema] Diagnose deprecated default implementations in the witness checker. #74244

hborla added 2 commits June 10, 2024 17:34
…cker.

If a protocol provides a deprecated default implementation for a requirement
that is not deprecated, the compiler should emit a warning so the programmer
can provide an explicit implementation of the requirement. This is helpful
for staging in new protocol requirements that should be implemented in
conforming types.

(cherry picked from commit 005b45c)
@hborla hborla requested a review from a team as a code owner June 11, 2024 00:40
@hborla
Copy link
Member Author

hborla commented Jun 11, 2024

@swift-ci please test

@hborla hborla merged commit 05b4363 into swiftlang:release/6.0 Jun 11, 2024
5 checks passed
@hborla hborla deleted the 6.0-deprecated-default-implementation branch June 11, 2024 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants