Skip to content

[ClangImporter] Switch lookupGlobalsAsMembers to take a non-optional EffectiveClangContext #74683

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
Jun 27, 2024

Conversation

hamishknight
Copy link
Contributor

The only caller is loadNamedMembers, and that passes in a non-optional EffectiveClangContext, meaning that we'd miss the case when getEffectiveClangContext returns nullptr, crashing in translateContext. No test case unfortunately as I haven't been able to come up with a reproducer.

rdar://129619711

…l EffectiveClangContext

The only caller is `loadNamedMembers`, and that
passes in a non-optional EffectiveClangContext,
meaning that we'd miss the case when
`getEffectiveClangContext` returns `nullptr`, crashing
in `translateContext`. No test case unfortunately
as I haven't been able to come up with a reproducer.

rdar://129619711
@hamishknight
Copy link
Contributor Author

@swift-ci please test

@hamishknight hamishknight merged commit 3168d54 into swiftlang:main Jun 27, 2024
5 checks passed
@hamishknight hamishknight deleted the null-context branch June 27, 2024 17:08
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.

2 participants