rip VS Clippy

I still use Rip (Rm Improved) even though it hasn't updated in 4 years https://github.com/nivekuil/rip . But a tool this simple doesn't need to

This looks like a nice replacement for the seemingly defunct rip: https://github.com/nivekuil/rip. Will definitely have to play around with this.

rip is an improved version of the rm command. It is faster, safer, and user-friendly. rip sends deleted files to a temp location so they can be recovered using rip -u. I really like the simplicity and the revert feature, as I don't have to worry about accidentally deleting something using rm. While rip can be aliased to replace rm, the creators advise not doing that as you might get used to it and do rm on other systems where you cannot revert the delete.

There is `rip`[1] (also written in Rust) which does more or less the same? Or am I missing something?

[1] https://github.com/nivekuil/rip

Looks nice, how does it compare to rip?

https://github.com/nivekuil/rip making people use things like that is scary, people really don't like change and i really don't like to preach anything for anyone. But i use it... i remember getting into arguments about CLI mp3 players and why they are stupid for my use case and i almost lost my mind, i don't want to be the person talking about RM lol.

I use rip for most things

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.