repi
repi
Fantastic, thanks for the heads up!
Ran into this again today with trying to upgrade to Rust 1.34 and where the [redundant_closure](https://rust-lang.github.io/rust-clippy/v0.0.212/#redundant_closure) had been enabled. All the cases it triggered on was for small member wrapper...
We now have 81 crates in our monorepo, all having to specify `#![warn(clippy::all)]` & co in every `lib.rs` to get the behavior we want here. It works but it is...
@YorickPeterse thanks, that does look like a workable solution for CI. Though for working locally for users and with tools like RLS I really want a solution where everyone can...
Yeah doesn't look like very active development of it unfortunately, but hope Cargo/Clippy gets it eventually. Just added these lines on top of 30 lib.rs files in our workspace to...
This is getting a bit more silly without this support, we have like 30 crates in our repo where all of their `lib.rs` start something like this: ```rust #![forbid(unsafe_code)] #!
We finally have a workaround for this that works quite well that we are transitioning our projects for, and that is to use `.cargo/config.toml` and set lint allow/deny CLI parameters...
Ah interesting, we are on Rust 1.55 and now with our v5 lint set (#67) it also requires 1.55 as we use new lints from it. Thought initially this approach...