[ConstraintSystem] Improvements to pattern binding checking #39079
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
Once coerced initializer expression has been set for a particular pattern binding entry, let's mark it as checked, otherwise decl checker might try to re-typecheck it.
Coercion should be aligned with `PatternBindingEntryRequest::evaluate` and that uses only one flag - `TypeResolverContext::PatternBindingDecl`.
…erty wrapper Assert that if there is an initializer it is already type-checked.
|
@swift-ci please smoke test |
hborla
approved these changes
Aug 30, 2021
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.
I couple of issues I have found while working on multi-statement closure type-checking.
setInitializerChecked