2 ms·
You should have it on for CI and for first party developers by default, but have it off if you distribute your source to third parties for the reason you stated
by IshKebab 3y ago
You should have it on for CI and for first party developers by default, but have it off if you distribute your source to third parties for the reason you stated.
That's kind of my point. C/C++ have a really bad implementation of warnings, which leads people to think that warnings are fundamentally a bad idea, which is not something I am convinced by.
- Gibbon1 3y agoI think people should look at the output of their compiler and fix warnings before checking in code. And frankly I'd rather the build not stop on the first error. In fact it would be best if the build system tried to link even if there are errors. Might work.
- IshKebab 3y ago> I think people should look at the output of their compiler and fix warnings before checking in code. I agree, but I don't think they should be required to fix all warnings before checking in code, which is what no-warnings languages like Go require. > And frankly I'd rather the build not stop on the first error. In fact it would be best if the build system tried to link even if there are errors. Might work. Not sure what your point is here. Most compilers don't stop on the first error.