fix: let_with_type_underscore don't eat closing paren in let (i): _ = 0;
#15386
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.
Apparently, one can surround a pattern with an arbitrary number of parens, and the resulting
Patwon't include the span of those parens. And the previous approach extended the to-be-deleted span all the way to the end ofPat's span, so it included the closing paren.I think the new approach is more robust anyway, since all we care to remove (besides the
_) is the:, so we search just for that.This does leave one extra whitespace in one of the test cases, but I'd say let rustfmt handle that.fixed in the third commitchangelog: [
let_with_type_underscore]: don't eat closing paren inlet (i): _ = 0;fixes #15377