3 ms·
Not having warnings is intentional and seen as a feature.
by nyberg 4y ago
Not having warnings is intentional and seen as a feature.
- dureuill 4y agoIt is a very unergonomic choice, though. Having warnings you can allow during development and deny in CI is the best of both worlds. Otherwise it leads to absurd situations where some code gets commented to avoid errors caused by unused things, which defeats the point of the lint. When coding in Rust, I extensively use warnings as a way to know what remains to be done before my code is done. Treating all warnings as errors all the time so as to address people who would ignore warnings is overtailoring the language for beginners at the price of ergonomics for experienced programmers.
- wizofaus 4y agoI'd agree with your last sentence if you included the inability to turn off specific warnings with source level directives. Otherwise (allowing compilation regardless of how many warnings there are) inevitably warnings do simply get ignored and just become "noise" in the compiler output.