commit | 0b898c9289f06f39229862be56335058001382ab | [log] [tgz] |
---|---|---|
author | Peter Weinbergr <pjw@google.com> | Mon Aug 03 13:09:45 2020 -0400 |
committer | Peter Weinberger <pjw@google.com> | Wed Aug 05 22:37:31 2020 +0000 |
tree | abf16db97109a958f24cfd5ba743a7355e7d0a83 | |
parent | f29cbc7105424c48527b8b420949cfe3d1d1a53c [diff] |
internal/lsp: add options to control which details gc_details shows The gc_details command, which shows the gc compiler's decisions, can produce thousands of diagnostics for a package. New gopls options 'noBounds', 'noEscape', 'noInline', 'noNilcheck' will suppress diagnostics of less interest to the user. These are in a new 'annotations' section parallel to 'codelens' or 'analyses'. Change-Id: Ica75de25b14f38b67ddfa9f997f581674f45221d Reviewed-on: https://go-review.googlesource.com/c/tools/+/246477 Run-TryBot: Peter Weinberger <pjw@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> 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.