Or just by not writing let _ =
replyAll recurrent people problems are system problems.
replyAs seen by the fact that forcing the programmer to write let _ = to silence the warning did not fix the bug.
replyYou know what might've solved this though? Using threads instead of async
Ehh, easy fix
reply #[allow(clippy::let_underscore_untyped,clippy::let_underscore_must_use)]
let _ = self.poll_flush(cx)?;I said ‘flagged’, not ‘fixed’ :)
replyYou can always write the wrong code if you want it enough. But hopefully a warning would have prompted someone to think harder about this flow.
But "let _ =" is already an explicit suppression of a must-use warning. Where does this arms race of "no, I really know what I am doing, compiler" versus "no, this really looks like a mistake, programmer" end?
replyThat's an excellent question I don't have an answer for in general :)
replyIMHO the goal is usually for the compiler not to make these decisions but to provide the tools for the APIs people build to make them. That's kind of passing the buck, though.
I guess in this case the core problem is that the API for these I/O calls has no representation in the type system for what's happening to the buffer. Proxying it as ‘the programmer must think about this code path’ is a reasonable best-effort but, evidently, sometimes inadequate.
I do feel like Rust did enough to allow software engineers and their managers to make an explicit choice here.
replyAnd this is why you should warn on `clippy::allow_attributes_without_reason` in your projects.
replyYou can set the lints to `forbid` instead of `deny`, which means they can't be `allowed` like that.
replyYeah, but you must know about them and the possible bug first in order to allow them...
replyHence ‘sadly’. IMNSHO both of these (or at least _untyped) should be enabled by default. Untyped `let _` is too big a footgun during refactorings.
replyAt which point you wouldn't have written this bug in the first place; or the warnings would trigger immediately, you'd change _ to an actual variable and then remove the warning pragmas because now you don't assign to _.
reply`Poll` is marked `#[must_use]` so if you were assigning to something other than `_` you'd get a warning that you're ignoring the `Pending` path. The Clippy lint is only for `_` which Rust considers a use by default.
replyNot really. If I'm using a linter, I go and configure the strictest possible ruleset, and only disable rules when justified on a need-by-need basis. It's just a matter of discipline.
reply[flagged]
reply