Go Analysis Framework: modular static analysis by go team
Documentation ¶ Overview ¶ Background Analyzer Pass Modular analysis with Facts Testing an Analyzer Standalone commands Package analysis defines the interface between a modular static analysis and an analysis driver program. Background ¶A static analysis is a function that inspects a package of Go code and reports a set of diagnostics (typically mistakes in the code), and perhaps produces other results as well, such as suggested refactorings or other facts. An analysis that reports mistakes is informally called a "checker".
- ▪Documentation ¶ Overview ¶ Background Analyzer Pass Modular analysis with Facts Testing an Analyzer Standalone commands Package analysis defines the interface between a modular static analysis and an analysis driver program.
- ▪Background ¶A static analysis is a function that inspects a package of Go code and reports a set of diagnostics (typically mistakes in the code), and perhaps produces other results as well, such as suggested refactorings or other facts.
- ▪An analysis that reports mistakes is informally called a "checker".
Hacker News (Front Page) files mainly under programming. We currently carry 607 of its stories. Top-voted stories on Hacker News.
Opening excerpt (first ~120 words) tap to expand
Documentation ¶ Overview ¶ Background Analyzer Pass Modular analysis with Facts Testing an Analyzer Standalone commands Package analysis defines the interface between a modular static analysis and an analysis driver program. Background ¶A static analysis is a function that inspects a package of Go code and reports a set of diagnostics (typically mistakes in the code), and perhaps produces other results as well, such as suggested refactorings or other facts. An analysis that reports mistakes is informally called a "checker". For example, the printf checker reports mistakes in fmt.Printf format strings.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Go.
Discussion
0 commentsMore from Go
