Skip to content

AST: Remove Decl::getSemanticAvailableRangeAttr() #77950

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

tshortli
Copy link
Contributor

@tshortli tshortli commented Dec 4, 2024

This query's functionality was not useful enough to be exposed on Decl and cached in the request evaluator. Instead, just share a local implementation of it in TypeCheckAttr.cpp.

@tshortli tshortli force-pushed the remove-semantic-available-range-attr branch from 4c6331d to 79c0900 Compare December 5, 2024 16:53
@tshortli
Copy link
Contributor Author

tshortli commented Dec 5, 2024

@swift-ci please smoke test

@tshortli tshortli enabled auto-merge December 5, 2024 16:53
This query's functionality was not useful enough to be exposed on `Decl` and
cached in the request evaluator. Instead, just share a local implementation of
it in `TypeCheckAttr.cpp`.
@tshortli tshortli force-pushed the remove-semantic-available-range-attr branch from 79c0900 to 4da7f83 Compare December 5, 2024 23:47
@tshortli
Copy link
Contributor Author

tshortli commented Dec 5, 2024

@swift-ci please smoke test

@tshortli tshortli merged commit aeb475b into swiftlang:main Dec 6, 2024
3 checks passed
@tshortli tshortli deleted the remove-semantic-available-range-attr branch December 6, 2024 16:51
tshortli added a commit to tshortli/swift that referenced this pull request Feb 3, 2025
When diagnosing a declaration that is more available than its context, to
preserve source compatibility we need to downgrade the diagnostic to a warning
when the outermost declaration is an extension. This logic regressed with
swiftlang#77950 and my earlier attempt to fix
this (swiftlang#78832) misidentified what had
regressed.

Really resolves rdar://143423070.
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.

1 participant