Skip to content

Sema: Suppress unavoidable deprecation diagnostics in _Concurrency #70912

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

Conversation

tshortli
Copy link
Contributor

The _Concurrency module must use some deprecated declarations in its implementation in order to maintain backward compatibility. Since these references are unavoidable, the deprecation diagnostics emitted about them are an unhelpful nuisance. This change introduces targetted logic for suppressing these specific deprecation diagnostics as a workaround until there is a language feature for suppressing deprecation diagnostics.

Also, remove a couple of superfluous trys.

The _Concurrency module must use some deprecated declarations in its
implementation in order to maintain backward compatibility. Since these
references are unavoidable, the deprecation diagnostics emitted about them are
an unhelpful nuisance. This change introduces targetted logic for suppressing
these specific deprecation diagnostics as a workaround until there is a
language feature for suppressing deprecation diagnostics.
@tshortli
Copy link
Contributor Author

@swift-ci please test

Copy link
Contributor

@ktoso ktoso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, thank you! Yeah sadly it's unavoidable to touch those so this is a good solution, lgtm!

@tshortli tshortli merged commit 8ae3c9e into swiftlang:main Jan 14, 2024
@tshortli tshortli deleted the suppress-concurrency-deprecation-diags-in-stdlib branch January 14, 2024 16:47
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