[Property Wrappers] Don't inject the wrapped value placeholder in CSApply if the apply expression is a nullptr #33238
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
in CSApply if the apply expression is a nullptr. The can happen for subscript calls because coerceCallArguments is called with a nullptr ApplyExpr.
|
@swift-ci please smoke test |
xedin
approved these changes
Jul 31, 2020
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 can happen for subscript calls because
coerceCallArgumentsis called with a nullptr for theApplyExpr.This caused CSApply to inject the wrapped value placeholder around subscript arguments for subscript calls inside the wrapper attribute when no wrapped value is specified via
=.Resolves: rdar://problem/66045798