@aescling I get somewhat overwhelmed when the compiler prints out more error messages than fit on the screen (and I have a big 1920x1080 screen!)

So for my own stuff (that doesn't already have -Wall -Werror set by the Makefiles or CMake or whatever), the approach is to first fix all the errors and get it to compile at all (usually it's just stupid mistakes like typoing the variable names or such, quick to fix), and maybe then to enable -Wall after that.

(It is good that a compiler can warn about potential mistakes, I just want to worry about that after I've fixed the real mistakes and not before that)

I do not see the point in -Werror, why would you want the compiler to refuse to compile code that it is totally capable of compiling?

(I keep complaining about how GCC14 made implicit int and implicit function declaration be errors by default rather than warnings... It breaks a ton of legacy code for no good reason... Hate it hate it hate it)

@aescling What about you?

@vaporeon_ usually, yeah

@aescling What's the point of the -Werror?

(Also, do you use Valgrind or Asan or anything? I think they're very useful when debugging a segmentation fault, or just confirming that no out-of-bound memory accesses happen in normal operation)

@vaporeon_ i like using a strict linter; it can catch logic errors