-
### Summary
Playground to the sample working code:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=f728413bb6ef3793b4075f6b51fc8a2a
Clippy suggests changing the main f…
-
Maybe add a clippy like character (an animated "M" with googly eyes) to serve the program.
-
### Summary
I don't have any code yet, I noticed this checking `rustc_mir_dataflow` with clippy that it seemed to hang.
### Reproducer
I tried this code:
```rust
```
I expected to see thi…
-
Using 1.59.0-beta.3, the following illustrates the point:
```
warning: missing `#[must_use]` attribute on a method returning `Self`
--> libp2p-streaming-response/src/v2/behaviour.rs:32:5
|
…
rkuhn updated
2 years ago
-
### Description
@yozhgoor and I discovered that the `--tests` option exists but is not listed in any of these commands:
- `cargo clippy --help`,
- `cargo clippy -- --help`,
- `clippy-driver …
-
### Summary
When an immutable reference is held, Clippy still suggests using `get_mut()` instead of `lock()` for Mutexes, even though this does not work, since it cannot borrow a mutable reference at…
-
Consider this code:
```rust
fn main() {
let mut a = vec![String::new()];
let b = vec![10];
a = b;
}
```
When using "cargo check" the error message uses trimmed type paths and i…
-
I was looking at rls which has this warning
````
error: calls to `std::mem::drop` with a value that implements Copy. Dropping a copy leaves the original intact.
--> rls-rustc/src/lib.rs:22:5
…
-
We should fix these, as suggested by @filnet there: https://github.com/dimforge/nalgebra/pull/788#issuecomment-727899092
-
This is a tracking issue for the RFC "Clippy 1.0" (https://github.com/rust-lang/rfcs/pull/2476).
**Steps:**
- [x] `shadow_unrelated` should be moved from `restriction` to `pedantic`
- [x] `exp…