Sema: Fix null dereference in overApproximateAvailabilityAtLocation()
#72742
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
The `TypeRefinementContext::findMostRefinedSubContext()` method can return `nullptr` in some circumstances, which means that callers need to check the result before dereferencing it in order to avoid a crash. I haven't introduced a test case because I can only reproduce the circumstances under which `findMostRefinedSubContext()` returns `nullptr` with a specific project that is exercising a bug in Swift macros. The fix here is obvious enough hardening, though. Resolves rdar://125054962
|
@swift-ci please smoke test |
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.
The
TypeRefinementContext::findMostRefinedSubContext()method can returnnullptrin some circumstances, which means that callers need to check the result before dereferencing it in order to avoid a crash. I haven't introduced a test case because I can only reproduce the circumstances under whichfindMostRefinedSubContext()returnsnullptrwith a specific project that is exercising a bug in Swift macros. The fix here is obvious enough hardening, though.Resolves rdar://125054962