3 ms·
What you really want for working on a large scale codebase is "don't allow changes that introduce new warnings". And with current tooling that's something you c
by lmm 3y ago
What you really want for working on a large scale codebase is "don't allow changes that introduce new warnings". And with current tooling that's something you can only really enforce at CI level if at all, but it shouldn't be that way. I'd like to have the same thing early in the test-edit cycle - compiling with a newer compiler that adds more warnings shouldn't be an error, but a code change that triggers a new warning should be.