lolbinarycat

fair, but how easy is the rest of that list, actually? contributing to clippy can be expecially rough due to the relative lack of issue triage

It also seems to forbid leading and trailing whitespace.

> > This would be especially interesting if Rust supported making every function `must_use` by default, since in practice small minority of functions have a discardable result (as demonstrated by...

> > I don't really like this approach because, well, error handling exists for a reason. If the error doesn't matter in a large number of cases, then you should...

> That's fair, although generally, iterator types aren't marked must_use; only functions returning iterators which do nothing unless used. For example, Vec::drain returns an iterator but doesn't mark it must_use,...

> Right, I guess that it's weird that the iterator as marked this way instead of the method, but I wouldn't necessarily say that this is an "exception rather than...

> My interpretation of a function returning `Result` is simply that the function might fail. The implication which follows from that is that the function could return an error that...

@Jules-Bertholet I would assume that would happen if/when regular `must_use` becomes meaningful in that position.

> Finally, a toolchain can be pruned if it's implicitly installed and all paths in its implicit.txt are invalid. Otherwise, only the invalid paths are removed instead. you would need...

that reccomendation doesn't appear anywhere in the documentation, and in fact [the visibility rules](https://docs.rs/ouroboros/0.18.4/ouroboros/attr.self_referencing.html#a-quick-note-on-visibility) seem to imply you can use it directly on a public struct.