commit | bdaa8bfb98b56b85d4d96c8190e7c8dd049ffcb5 | [log] [tgz] |
---|---|---|
author | Matthew Dempsky <mdempsky@google.com> | Fri Feb 19 11:05:58 2021 -0800 |
committer | Matthew Dempsky <mdempsky@google.com> | Fri Feb 19 19:26:32 2021 +0000 |
tree | 27a34204effb31d53431ec02ba6b786f1512070a | |
parent | f4301d9e1667ab2b9ce80475cd3ca1912f266258 [diff] |
go/gcexportdata: warn that {Read,Write}Bundle are experimental After playing with these a little, they definitely get the job done. But I'm already seeing a few ways the API could be nicer (e.g., provide a bundle-backed go/importer.Importer implementation that reads packages out on demand, so unneeded packages don't need to be read). So mark these APIs as experimental so users know not to get too attached to them just yet. Change-Id: Idb98f45095a0c6f9825ff07172f62c42d8453016 Reviewed-on: https://go-review.googlesource.com/c/tools/+/294310 Reviewed-by: Rebecca Stambler <rstambler@golang.org> Trust: Matthew Dempsky <mdempsky@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.