I'd prefer `eslint-expect-error-next-line` instead to warm me when the comment is actually useless but it's better than what Zig seem to do.
I do wish Rust had something like this too
You can put it at the top of your file with a #! too, if you want it to apply to the whole file.
pub fn abc() -> usize {
#[allow(deprecated)]
"abc".len()
}
I want it to complain about the "allow", because there was never any deprecated warning emitted in the first place. Maybe it would be called #[expect(deprecated)]I refactor code all the time and find these stray "allow"s that aren't doing anything anymore
Both this and the reply saying you should open an RFC worry me that it was tongue-in-cheek.
Or maybe it's the obvious name choice, heh, because it literally exists with that very syntax: https://play.rust-lang.org/?version=nightly&mode=debug&editi...
Not stable yet, as you can see, but all the RFC and implementation work has been done, and a stabilization report was even put forward back in July: https://github.com/rust-lang/rust/issues/54503#issuecomment-...
The strict compiler check would have had exactly the opposite effect from the intended one.