Sema: Correct availability for @inlinable global var accessors bodies #67850
+143
−26
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@swift-ci please test |
The bodies of unavailable functions should be typechecked as if they would always run at the deployment target, even if they are `@inlinable`. This was not the case in the bodies of unavailable `@inlinable` global var accessor, though, because the availability of the accessor, rather than enclosing var, was being queried. The fix is to use `getSemanticUnavailableAttr()`. Resolves rdar://113642576
tshortli
force-pushed
the
unavailable-inlinable-computed-property-availability
branch
from
e89b088 to
2cc1a93
Compare
|
@swift-ci please smoke test |
xymus
approved these changes
Aug 10, 2023
artemcm
approved these changes
Aug 10, 2023
tshortli
deleted the
unavailable-inlinable-computed-property-availability
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The bodies of unavailable functions should be typechecked as if they would always run at the deployment target, even if they are
@inlinable. This was not the case in the bodies of unavailable@inlinableglobal var accessors, though, because the availability of the accessor, rather than enclosing var, was being queried. The fix is to usegetSemanticUnavailableAttr().Resolves rdar://113642576