It's discussed fairly often with static analyzers. Static analysis is a powerful tool, but false positives erode user confidence in the tool. I've worked with

It's discussed fairly often with static analyzers. Static analysis is a powerful tool, but false positives erode user confidence in the tool. I've worked with code bases where thousands of warnings (and even several errors) were left in place, which meant that you had to basically ignore all diagnostic messages every time you compiled. At that point, you might as well be 2>/dev/null. Someone even wrote a wrapper script that would diff the stderr against the "known good" stderr. My general impression of that project was that it was dying a slow death unless someone went in and restored developer confidence in the build process, and the most likely person was me :-/