commit | 51cde5226ead67dcfd635a510180cc1417186271 | [log] [tgz] |
---|---|---|
author | Rebecca Stambler <rstambler@golang.org> | Fri Oct 30 20:01:13 2020 +0000 |
committer | Rebecca Stambler <rstambler@golang.org> | Mon Nov 02 01:26:20 2020 +0000 |
tree | 655e03eb0f53cbed26c4d0adfe79591ad43e70ce | |
parent | 1f28ee682075ddd58383833c7340c421a395e93e [diff] |
internal/lsp: move initialization entirely into the snapshot The majority of the initialization logic is already based on the snapshot, not the view, so it makes sense to move it there. The initialization status of the snapshot is copied and invalidated in clone. Fixes golang/go#41764 Change-Id: I93234b394318964e7af4696e5ebd465088a05728 Reviewed-on: https://go-review.googlesource.com/c/tools/+/266700 Trust: Rebecca Stambler <rstambler@golang.org> Run-TryBot: Rebecca Stambler <rstambler@golang.org> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
This subrepository holds the source for various packages and tools that support the Go programming language.
Some of the tools, godoc
and vet
for example, are included in binary Go distributions.
Others, including the Go guru
and the test coverage tool, can be fetched with go get
.
Packages include a type-checker for Go and an implementation of the Static Single Assignment form (SSA) representation for Go programs.
The easiest way to install is to run go get -u golang.org/x/tools/...
. You can also manually git clone the repository to $GOPATH/src/golang.org/x/tools
.
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.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, 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.