[Type checker] Cope with null function/subscript types but not error types #21506
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
…types. We always ensure that functions and subscripts have appropriately-shaped interface types, so the "error" check is unnecessary. However, if we end up in a recursive-validation case, the interface type *might* be null. Replace a check for the former with a check for the latter. Thanks @slavapestov.
|
@swift-ci please smoke test and merge |
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.
We always ensure that functions and subscripts have
appropriately-shaped interface types, so the "error" check is
unnecessary. However, if we end up in a recursive-validation case, the
interface type might be null. Replace a check for the former with a
check for the latter.
Thanks @slavapestov.