[CSGen] Don't increase optionality of weak var patterns
#39162
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
If the externally-imposed type is already optional, let's not add optionality to the pattern.
- Make sure that `varType` is wrapped into an optional type for `weak` declarations. - Verify that `externalPatternType` is an optional type when one-way constraints are requested.
hborla
approved these changes
Sep 4, 2021
|
@swift-ci please test |
|
@swift-ci please test source compatibility |
|
Source compatibility is UPASS. |
|
Whoa. Interesting. How did this not get caught until now? |
|
@davezarzycki because this code currently only applies to result builder bodies, and nobody has written a local |
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.
If the externally-imposed type is already optional,
let's not add optionality to the pattern.