cargo-deb VS Clippy

I mean, there's tools that make it easy to make a .deb https://crates.io/crates/cargo-deb

The Rust Project itself had put a lot of work into making sure that Rust and Rust-using programs could get into Debian by working with Debian folks to address issues.

I suspect that you've run into an anecdotal pattern, but I'm not sure that it is more than that.

I use Cargo deb to create Debian / Ubuntu / ... package files.

As a suggestion if you want to get a lot of users you could make a .deb file that packages the binary and a systemd service file. Using cargo-deb it's pretty trivial, the hardest part would be writing your systemd service file and you can probably just copy the dunst.service file with minimal modification:

https://crates.io/crates/cargo-deb https://github.com/kornelski/cargo-deb

cargo install does provide different options to change the installation dir (https://doc.rust-lang.org/cargo/commands/cargo-install.html) but I am uncertain, if there could be accociated issues. An alternative could be tools like https://github.com/mmstick/cargo-deb or https://github.com/iqlusioninc/cargo-rpm that can automatically create packages which can be used for a proper installation /usr/bin/ using your distributions packaging system.

Cargo already has one: https://crates.io/crates/cargo-deb

I couldn't find it in the API guidelines either. From what I understand, the idea is that any trait bounds, which includes generic type parameter bounds and lifetime bound on a type (struct or enum) would be repeated back in the impl block

there is a nice discussion on this issue here: https://github.com/rust-lang/rust-clippy/issues/1689

You should not blindly follow clippy lints. They are sometimes wrong. Another example https://github.com/rust-lang/rust-clippy/issues/9782 .

I often write () = f() to assert that f() is unit. Unfortunately clippy warns on such code ( https://github.com/rust-lang/rust-clippy/issues/9048 ). There are very recent pull requests for this bug, so hopefully this bug will be fixed very soon. But meanwhile I invented this workaround: [()] = [f()] :)

Apart from running clippy on many projects being essential, clippy is also an exceptionally welcoming project, no matter your prior knowledge.

clippy is a great place to get started :) though it isn't exactly new.

clippy is also pretty compiler-adjacent and unlike rust-analyzer uses rustc's internal APIs. Don't let the size of the code base scare you off! It's actually feasible for a newcomer to contribute even such a substantial change as a new lint, and we have issues labeled as "good first issue" that come with mentorship, so you don't need to go it alone.

Yes, you could use it to write a lint. Although you might find it easier to just fork Clippy and add your own lints to their existing framework.

Check out the readme for more information.

They are two of my favorite Rust tools. If you haven’t tried them yet, I highly recommend giving them a try. Clippy can detect various lints in your code and guide you towards writing more idiomatic code. To install Clippy, simply run rustup component add clippy, and to run it within your workspace, execute cargo clippy. For more details, visit Clippy’s GitHub repository.