| commit | c9a70fc28ce398a63d7835370de575fec20f826e | [log] [tgz] |
|---|---|---|
| author | Heschi Kreinick <heschi@google.com> | Wed Sep 16 14:40:39 2020 -0400 |
| committer | Heschi Kreinick <heschi@google.com> | Wed Sep 16 19:50:26 2020 +0000 |
| tree | 57d4d29e29331a6356177f5659121469110d7f01 | |
| parent | f128e626db139fbf9b0a715b07661464add0cf6b [diff] |
internal/lsp/cache: fix release tag parsing A copy and paste error meant that gopls iterated over the built-in release tags rather than the ones read from go list. If gopls was built with an older release than the go command in use, it would read past the end of the slice and die. Change-Id: Ifc222c7a0bd9662bcd7deedaa069797e213df7b3 Reviewed-on: https://go-review.googlesource.com/c/tools/+/255360 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Go Bot <gobot@golang.org> gopls-CI: kokoro <noreply+kokoro@google.com> Reviewed-by: Rebecca Stambler <rstambler@golang.org>
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.