4 ms·
Exactly. -Wextra should also be in the same boat as -Werror and -Wall. How to deal with different toolchains having different approaches to what warnings are
by outsomnia 5y ago
Exactly. -Wextra should also be in the same boat as -Werror and -Wall.
How to deal with different toolchains having different approaches to what warnings are enabled? Assertively disable the handful of stupid warnings like -Wno-unused-parameter, and have your CI encompass most toolchains such that the union of their warnings is your target and break build if any blow warnings.
Then you will have something robust and portable.
- saagarjha 5y agoRobust and portable, until someone tries compiling it with LLVM 13 that you haven't tested on…
- outsomnia 5y ago> Robust and portable, until someone tries compiling it with LLVM 13 that you haven't tested on… Yes, new compilers are able to get new insight into what is broken with your code. You can either: a) ignore that and let your users continue with the brokenness, since that is convenient at build-time (but the consequent failures in the field of whatever that code is integrated in may be extremely inconvenient for all downstream users) b) learn about it, and fix your code upstream so all users can benefit from the fixes