[refurb] Avoid panicking unwrap in verbose-decimal-constructor (FURB157)
#16777
+196
−12
Conversation
This file contains 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
dylwil3
added
bug
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.
Removes
find/unwrapin creating fix for verbose-decimal-constructor (FURB157).Previously, we tried to maintain trivia such as whitespace, implicitly concatenated strings, etc. when replacing something that parses to the value
"-nan". This requires too much complexity when the user has unicode escape sequences such as"\N{character tabulation}\N{hyphen-minus}nan". So in this case we just replace the string literal with exactly"nan".Closes #16771