I&#x27;m not going to dispute that #7 earns a place lower down the chain than the features you mentioned in practical terms of identifying bugs. That said, it&#x27;s only overly feasible when run from early on in design.<p>If a project currently produces clean output, and I make a commit that causes clang&#x27;s analyser to complain, it&#x27;s easy enough to fix, whether it&#x27;s a &quot;legitimate&quot; error or not.<p>I&#x27;ve tried throwing static analyzers at long established projects like OpenSSL and.. there&#x27;s just no point. Noone is going to review a few thousand errors and make hundreds of commits that don&#x27;t actually fix anything just to get perfectly clean static analysis output. It&#x27;s more likely I would break something than help.<p>It&#x27;s really not that hard to implement a &quot;no commit unless it passes static analysis&quot; rule from the start, and even if the bugs removed are low, I usually argue they are non-zero.