In the proposed context "developers should", yeah, it totally makes sense. You've got different categories of warnings: Things that are harmless but trivial t

In the proposed context "developers should", yeah, it totally makes sense. You've got different categories of warnings: Things that are harmless but trivial to fix - so why not fix them. Things that are valid in this specific context - they probably deserve a comment / pragma / explicit disabling. Things that are real issues that should be fixed but won't stop the compilation - and if they're invisible because of the noise of the previous 3 categories, you're going to have issues. Just today had to fix two things which had warnings available for a long time and with the recent clang they became an error. They shouldn't been fixed upstream ages ago, but they were ok with the warnings.