Identifiers beginning with '__' are not required to be snake case #32683
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 change fixes #32653. As suggested by @pnkfelix, a snake case check will return true when the string begins with '__', even if it is not snake case.
This code normally produces an error:
format!("foo {N}", N=name)
This happens because the code generates a variable named
__argN
, which does not comply with the snake case lint. However, under the patch, that would not cause the lint to throw a warning because it begins with two underscores.