Skip to content

Break dependency cycle between @objc checking and and "renamed" availability #60982

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
merged 1 commit into from
Sep 7, 2022

Conversation

DougGregor
Copy link
Member

The filtering used to allow @objc protocols to have both an async 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.

…ilability.

The filtering used to allow `@objc` protocols to have both an `async` 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.
@DougGregor
Copy link
Member Author

@swift-ci please smoke test

@DougGregor DougGregor merged commit d2f6107 into swiftlang:main Sep 7, 2022
@DougGregor DougGregor deleted the objc-async-alternative-cycle branch September 7, 2022 23:58
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