3 ms·

A common trope that is probably ignored or even unknown to uninformed C/C++ programmers, is that -Werr should be used for debug builds (as you use during develo

by j1elo 2y ago

A common trope that is probably ignored or even unknown to uninformed C/C++ programmers, is that -Werr should be used for debug builds (as you use during development) and never for release builds (as otherwise it will most probably break compilation in future releases of the compiler)

motorest 2y ago
> A common trope that is probably ignored or even unknown to uninformed C/C++ programmers, is that -Werr (...) Not even that. -Wall -Werror should be limited to local builds, and should never touch any build config that is invoked by any pipeline.
- IshKebab 2y ago
  No you definitely want to enforce this in CI.
  - motorest 2y ago
    > No you definitely want to enforce this in CI. No, not really. It makes absolutely no sense to block builds for irrelevant things as passing unused arguments to a function.
    - jpc0 2y ago
      -Werror= and you can error on decide which warnings are errors. No reason to enable it globally
    - IshKebab 2y ago
      > irrelevant things as passing unused arguments to a function. That's not irrelevant. I have seen many bugs detected by that warning.