4 ms·
The problem boils down to compilers not having multiple classes of warnings. If you do an assignment in a conditional? Yeah, that's a good thing to warn the use
by phendrenad2 5y ago
The problem boils down to compilers not having multiple classes of warnings. If you do an assignment in a conditional? Yeah, that's a good thing to warn the user about. Heck, that should be an error IMHO. But if I leave in a variable declaration, should my entire build crash to a halt because of the unused variable?
Presumably Google and any other engineering org of any value has their own set of warnings and errors layered on top of the clang/gcc warning/error output. We should try to learn from them, and carry that upstream, rather than bludgeon everyone over the head with a frankly simplistic "warnings bad mmmkay".