commit | a43f69b1f5e22e6a9892effdfa50d1f867db4c89 | [log] [tgz] |
---|---|---|
author | Rob Findley <rfindley@google.com> | Thu Feb 18 19:44:30 2021 -0500 |
committer | Robert Findley <rfindley@google.com> | Tue Feb 23 18:29:07 2021 +0000 |
tree | 4bfc4f969c1dc7b7e6caa0183181d54cd2faa800 | |
parent | f48e60bd82e7306b5f616fc93f697a45d25e28db [diff] |
go/expect: use parser.AllErrors when extracting Notes Without this parser mode, go/parser will bail out and return no comments from a parsed file if there are more than 10 errors. This can lead to tests silently not running, as noted in the TODO right above the parse. This can still happen: poor parser recovery could result in comments not being parsed. However, the parser is generally pretty good about preserving comments, and anyway passing parser.AllErrors means that adding a single new error to a testdata file will not suddenly cause all errors in that file to be ignored. Change-Id: Ib3c22944999651018d38fa6ce5c5a11ac6853aa0 Reviewed-on: https://go-review.googlesource.com/c/tools/+/293932 Trust: Robert Findley <rfindley@google.com> Run-TryBot: Robert Findley <rfindley@google.com> 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.