▲ | Announcing the Clippy feature freeze(blog.rust-lang.org) | |||||||
67 points by jmillikin 8 hours ago | 7 comments | ||||||||
▲ | andy_ppp 6 hours ago | parent | next [-] | |||||||
FYI “Rust’s Clippy is a collection of lints (static analysis rules) designed to catch common mistakes and suggest improvements in your Rust code.” | ||||||||
| ||||||||
▲ | lewdwig 5 hours ago | parent | prev | next [-] | |||||||
If Clippy struggles to account for current and future changes to the Rust compiler this to me raises an obvious question: why isn’t Clippy part of the Rust compiler? | ||||||||
| ||||||||
▲ | ishanjain28 3 hours ago | parent | prev | next [-] | |||||||
Unrelated, Is there a clippy lint to detect when you fill up and array/collection and immediately call clear on it ? | ||||||||
▲ | PartiallyTyped 6 hours ago | parent | prev | next [-] | |||||||
I’ve contributed quite a few patches into clippy, it’s a great project and a great way to learn how the rustc “sees” code; from the AST, to HIR, to using typeck — sometimes we even construct types at runtime to validate the code against — to tracking traits and their implementations across a whole crate! Clippy really is a labour of love project, and it’s been great to work with these folk <3 I will try to pick up some issues in the coming weeks. | ||||||||
▲ | jedisct1 4 hours ago | parent | prev [-] | |||||||
Just to be clear, this has nothing to do with Microsoft Clippy. This post is about a tool for a programming language called Rust. |