Break dependency cycle between @objc
checking and and "renamed" availability
#60982
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 filtering used to allow
@objc
protocols to have both anasync
and a completion-handler version of the same method was dependent on the resolution of the "renamed" declaration (for@available(..., renamed: "")
), which in tern was dependent on whether the declaration is@objc
... causing a cycle. Break the cycle by moving the filtering later.Fixes rdar://99618060.