This is some smooth trolling of the GCC mailing list. The April Fools went right over two people's heads. https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00002.html …
-
I'm actually a believer in using -Werror, even on the build systems. If you update your tooling you should revalidate anyway and new warnings very well might be important and need immediate addressing.
If you're releasing binaries, sure. If you're releasing source, no. There's no point in making users' builds break with new compiler warnings (which the vast majority of the time are indicative of problems that were already there to begin with).
-
-
Having worked with build systems for a few years, I can say this is a problem. Keeping track of which code builds with -Werror and which does not. Of course you want to build with zero warnings, but being warning-free does little for validating your build, running the code does.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.