Improve pattern recognition in UseLetInEveryBoundCaseVariable.
#244
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
This rule was previously flagging uses of `let/var` that don't apply (such as `let x as Y`). This commit also includes improvements to drill through optional patterns (e.g., `case let .foo(x)?`) and now handles tuple patterns as well (e.g., `case let (x, y)`). Fixes SR-11773.
|
cc @dylansturg |
dylansturg
approved these changes
Oct 26, 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.
This rule was previously flagging uses of
let/varthat don'tapply (such as
let x as Y). This commit also includesimprovements to drill through optional patterns (e.g.,
case let .foo(x)?) and now handles tuple patterns as well(e.g.,
case let (x, y)).Fixes SR-11773.