[5.9] [SymbolGraphGen] don't emit symbols and protocols from unconditionally unavailable extensions #67540
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
…ensions rdar://112137607
|
@swift-ci Please test |
|
@swift-ci Please test Linux |
airspeedswift
approved these changes
Jul 26, 2023
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.
Cherry-pick of #67539
Explanation: Prevents protocols and symbols added via unconditionally-unavailable extensions from appearing in symbol graphs.
Scope: Affects documentation of projects that use this pattern to forbid protocols like
Sendable.Issue: rdar://112137607
Risk: Low. This fix is targeted to SymbolGraphGen, doesn't affect normal compilation, and hides symbols and relationships that should be considered unavailable.
Testing: Automated tests have been added to ensure the new behavior.
Reviewer: @daniel-grumberg