| commit | 61e2d3f4fee1a8fb382d357fadc53af7828054c0 | [log] [tgz] |
|---|---|---|
| author | Alan Donovan <adonovan@google.com> | Fri Oct 14 17:58:15 2022 -0400 |
| committer | Alan Donovan <adonovan@google.com> | Mon Dec 19 15:59:49 2022 +0000 |
| tree | a5a7e093c5c9ded87d685d91f90fda3ad57f1dd3 | |
| parent | eb70795aaccb8e6c9615c88085ef3414ba04b8c9 [diff] |
gopls/internal/lsp/cache: a new analysis driver This change is a new implementation of gopls' analysis driver that supports "facts" (separate analysis across packages), and serializes the results of each unit of analysis in a global, persistent, file-based cache of bounded size with LRU eviction (filecache). Dependency analysis is based on hashes of only material inputs to each step: source files, and the types and facts of direct dependencies. Therefore changes that do not affect these (e.g. the insertion of a debugging print statement into a function body) will usually not invalidate most of the graph. Fact serialization is shared with unitchecker, though perhaps there are gains to be made by specializing it in future. This change uses the new API for shallow export data, in which only the types for a single package are emitted, not all the indirectly reachable types. This makes the size of the export data for each package roughly constant, but requires that export data for all transitive dependencies be available to the type checker. So, the analysis summary holds a map of all necessary export data as a union across dependencies. (It's actually somewhat fewer than all transitive deps because we record the set of packages referenced during type checking and use that to prune the set.) Change-Id: I969ce09c31e2349f98ac7dc4554bf39f93a751fe Reviewed-on: https://go-review.googlesource.com/c/tools/+/443099 Reviewed-by: Tim King <taking@google.com> Reviewed-by: Robert Findley <rfindley@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Alan Donovan <adonovan@google.com> gopls-CI: kokoro <noreply+kokoro@google.com>
This repository provides the golang.org/x/tools module, comprising various tools and packages mostly for static analysis of Go programs, some of which are listed below. Use the “Go reference” link above for more information about any package.
It also contains the golang.org/x/tools/gopls module, whose root package is a language-server protocol (LSP) server for Go. An LSP server analyses the source code of a project and responds to requests from a wide range of editors such as VSCode and Vim, allowing them to support IDE-like functionality.
Selected commands:
cmd/goimports formats a Go program like go fmt and additionally inserts import statements for any packages required by the file after it is edited.cmd/callgraph prints the call graph of a Go program.cmd/digraph is a utility for manipulating directed graphs in textual notation.cmd/stringer generates declarations (including a String method) for “enum” types.cmd/toolstash is a utility to simplify working with multiple versions of the Go toolchain.These commands may be fetched with a command such as
go install golang.org/x/tools/cmd/goimports@latest
Selected packages:
go/ssa provides a static single-assignment form (SSA) intermediate representation (IR) for Go programs, similar to a typical compiler, for use by analysis tools.
go/packages provides a simple interface for loading, parsing, and type checking a complete Go program from source code.
go/analysis provides a framework for modular static analysis of Go programs.
go/callgraph provides call graphs of Go programs using a variety of algorithms with different trade-offs.
go/ast/inspector provides an optimized means of traversing a Go parse tree for use in analysis tools.
go/cfg provides a simple control-flow graph (CFG) for a Go function.
go/expect reads Go source files used as test inputs and interprets special comments within them as queries or assertions for testing.
go/gcexportdata and go/gccgoexportdata read and write the binary files containing type information used by the standard and gccgo compilers.
go/types/objectpath provides a stable naming scheme for named entities (“objects”) in the go/types API.
Numerous other packages provide more esoteric functionality.
This repository uses Gerrit for code changes. To learn how to submit changes, see https://golang.org/doc/contribute.html.
The main issue tracker for the tools repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/tools/(your subdir):” in the subject line, so it is easy to find.
This repository uses prettier to format JS and CSS files.
The version of prettier used is 1.18.2.
It is encouraged that all JS and CSS code be run through this before submitting a change. However, it is not a strict requirement enforced by CI.