News for hackers. Stuff that matters.

A comment on Speeding Up the Rust Compiler. Parent comment

Re:Speeding Up the Rust Compiler by jayflux on Wednesday December 11, 2019 @08:54AM (#21762285)
I’m pretty sure clippy “encourages” you to use .get() for Vectors returning an Option<> for you to deal with so accessing a bad index is avoidable in idiomatic rust.

I’m not sure that was the best example but I agree with your overall point.

[ Parent | on HN ]
Re:Speeding Up the Rust Compiler by burntsushi on Wednesday December 11, 2019 @09:20AM (#21762524)
It does not. I know because I advocated against it. :-) https://github.com/rust-lang/rust-clippy/issues/1300

Also, Clippy's defaults are developed to be quite opinionated. It makes many suggestions that I (and many others) disagree with. So Clippy's defaults should not be used as a bludgeon for what's idiomatic and correct.

[ Parent | on HN ]
Re:Speeding Up the Rust Compiler by steveklabnik on Wednesday December 11, 2019 @10:14AM (#21763095)
(I also do not use clippy very aggressively due to disagreeing with a lot of lints)
[ Parent | on HN ]
Re:Speeding Up the Rust Compiler by GrayShade on Wednesday December 11, 2019 @09:12AM (#21762473)
It doesn't: https://play.rust-lang.org/?version=stable&mode=debug&editio... (click Tools / Clippy).
[ Parent | on HN ]