[5.6][SymbolGraph] don't filter out all implicit decls #41167
Merged
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
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 #41141
Explanation: Implicitly-generated initializers are not present in symbol graphs, even when the
-minimum-access-levelis set tointernal. Other sources of symbol information, like SourceKit, properly show these initializers, so their absence in symbol graphs is an issue.Scope: Only affects users of SymbolGraphGen who request symbol graphs with
internalaccess or below.Issue: rdar://86294494
Risk: Low. This change is limited to SymbolGraphGen, and does not affect normal compilation.
Testing: A new lit test,
SymbolGraph/Symbols/Implicit, was added to verify the new behavior.