Fix incorrect cast target #19093
Merged
Fix incorrect cast target #19093
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
Found while updating #18285 to latest master. Not sure what this fixes, but it was definitely incorrect - `node` must be a `Block` at this point, so this cast must have been intended for `node.parent`, which was checked against `TryStatement` right before it.
Member
Author
|
@amcasey does whatever this affects have test coverage? I saw no test diff locally before or after this change. |
Member
|
@weswigham There appears not to be coverage for this particular code path. I'll add a test after you merge. |
amcasey
approved these changes
Oct 11, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Found while updating #18285 to latest master. Not sure what this fixes, but it was definitely incorrect -
nodemust be aBlockat this point, so this cast must have been intended fornode.parent, which was checked againstTryStatementright before it.Hopefully this example can be further incentive that we'd really like to be using a discriminated union of node types. 🐱