[5.2] [CSSimplify] Guard against null locator #29889
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
xedin
approved these changes
Feb 17, 2020
tkremenek
approved these changes
Feb 17, 2020
|
@swift-ci please 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.
Explanation:
resolveValueMembercallsCS.performMemberLookupwith null locator, which is later passed toisSelfRecursiveKeyPathDynamicMemberLookup. This leads to a crash while indexing. Make sure the locator is not null before accessing it.Issue: SR-12174 | rdar://problem/59496015
Scope: Affects use of
@dynamicMemberLookupwith default implementations.Risk: Very Low. This is a regression from Swift 5.1 which is now fixed.
Testing: Added compiler regression test.
Reviewed by: @xedin
Cherry-pick of #29886