| Age | Commit message (Collapse) | Author | Lines |
|---|
|
|
|
|
|
Closes #21735.
|
|
|
|
|
|
Additionally, add lots of tests for new functionality around statics and
`static mut`.
|
|
This unifies the `non_snake_case_functions` and `uppercase_variables` lints
into one lint, `non_snake_case`. It also now checks for non-snake-case modules.
This also extends the non-camel-case types lint to check type parameters, and
merges the `non_uppercase_pattern_statics` lint into the
`non_uppercase_statics` lint.
Because the `uppercase_variables` lint is now part of the `non_snake_case`
lint, all non-snake-case variables that start with lowercase characters (such
as `fooBar`) will now trigger the `non_snake_case` lint.
New code should be updated to use the new `non_snake_case` lint instead of the
previous `non_snake_case_functions` and `uppercase_variables` lints. All use of
the `non_uppercase_pattern_statics` should be replaced with the
`non_uppercase_statics` lint. Any code that previously contained non-snake-case
module or variable names should be updated to use snake case names or disable
the `non_snake_case` lint. Any code with non-camel-case type parameters should
be changed to use camel case or disable the `non_camel_case_types` lint.
[breaking-change]
|
|
The old syntax will be removed after a snapshot.
RFC #47.
Issue #16461.
|
|
This updates identifier warnings such as ``struct `foo_bar` should have a
camel case identifier`` to provide an example.
Closes #14738.
|
|
Closes #2569
|
|
|
|
|
|
This is to clarify that the lint is checking for THIS_THING and not This.
|
|
This tries to warn about code like:
```rust
match (0,0) {
(0, aha) => { ... },
...
}
```
where `aha` is actually a static constant, not a binding.
|
