| commit | 0aa4b8830f481fed77b73cf7cea2bc3129e05148 | [log] [tgz] |
|---|---|---|
| author | Michael Matloob <matloob@golang.org> | Tue Aug 21 17:35:57 2018 -0400 |
| committer | Michael Matloob <matloob@golang.org> | Tue Sep 04 20:52:37 2018 +0000 |
| tree | efc7978e3e14db51b0ee59aa5bea61e3ddbcf363 | |
| parent | 18b2bbde9dd0ec9af0dcc5779baf873c36f89fff [diff] |
go/packages: remove the Config.Error hook Errors relating to a particular package (as opposed to the Load operation as a whole) are now only recorded in the Errors field of the corresponding Package. Clients are responsible for printing or otherwise handling errors. This is a breaking API change. The PrintErrors function prints all accumulated errors, dependencies first, and is provided for convenience. PrintErrors is based on Visit, another helper function, which visits each Package in an import graph. Also: - add an Example documenting typical use. - update clients to handle errors explicitly. Depends on https://go-review.googlesource.com/c/tools/+/130576 Change-Id: I39407ab7f46dae2f0dd0fdde21080e172e1258aa Reviewed-on: https://go-review.googlesource.com/131015 Reviewed-by: Michael Matloob <matloob@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 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.