Re:Useful GCC warning options not enabled by -Wall -Wextra
by quotemstr on Wednesday October 04, 2017 @04:57PM
(#15404576)
In Java, the compiler complains about unreachable code and aborts. I think that's ridiculous. Sometimes it's useful to create unreachable code during development.
int foo = doSomething();
return 0; // Debug XXX DONOTSUBMIT
int bar = doSomethingElse();
return foo + bar;
It's hilarious, though, that this workaround works: int foo = doSomething();
if (1 > 0) return 0; // Debug XXX DONOTSUBMIT
int bar = doSomethingElse();
return foo + bar;
Go's mandatory warnings are equally annoying. I'm sick and tired of little rarefied groups of language designers trying to impose their ideas about best practices on the rest of the world.
Re:Useful GCC warning options not enabled by -Wall -Wextra
by wruza on Wednesday October 04, 2017 @05:53PM
(#15405047)
What did you expect from a language that dictates to where to put your opening brace.
Re:Useful GCC warning options not enabled by -Wall -Wextra
by vkou on Wednesday October 04, 2017 @08:34PM
(#15405978)
What? That's a common style choice, not a language requirement.
Re:Useful GCC warning options not enabled by -Wall -Wextra
by ameliaquining on Wednesday October 04, 2017 @11:29PM
(#15406526)
You can't put the opening brace of a block on a separate line in Go, because the parser will insert a semicolon before it.
Warnings in that case are still useful. If the project is otherwise warning-free then it's easy enough to spot the new warnings and judge if they represent a real mistake.
My preference today is to set -Werror on CI builds. Any code that's final should be warning-free, but it's unnecessarily painful for work-in-progress.