Lessons from Building Static Analysis Tools at Google

Lessons from Building Static Analysis Tools at Google

  • April 30, 2018
Table of Contents

Lessons from Building Static Analysis Tools at Google

Here, we describe how we have applied the lessons from Google’s previous experience with FindBugs Java analysis, as well as from the academic literature, to build a successful static analysis infrastructure used daily by most software engineers at Google. Google’s tooling detects thousands of problems per day that are fixed by engineers, by their own choice, before the problematic code is checked into Google’s companywide codebase.

Source: acm.org

Tags :
Share :
comments powered by Disqus

Related Posts

Notes on structured concurrency, or: Go statement considered harmful

Notes on structured concurrency, or: Go statement considered harmful

In this post, I want to convince you that nurseries aren’t quirky or idiosyncratic at all, but rather a new control flow primitive that’s just as fundamental as for loops or function calls. And furthermore, the other approaches we saw above – thread spawning and callback registration – should be removed entirely and replaced with nurseries.

Read More