| commit | f1c1faf65a94bd57d856f83f39af12fbb8c04c80 | [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:04:35 2018 +0000 |
| tree | 99525b81dfc647caf5208dbbc7dbb88ba5e24e69 | |
| parent | 7ca132754999accbaa5c1735eda29e7ce0f3bf03 [diff] |
go/packages: coerce all errors to a single type Rather than document the range of possible error types, requiring clumsy client code to extract position information, we now expose a single concrete type for all errors. Position information (in standardized string form) is technically optional, but we should strive for 100%, fixing gaps as they arise. This change enables us to unify the Package and JSON structs in a follow-up. Question: should we eliminate the Config.Error hook and be silent by default? Pro: + most clients suppress it. Con: - clients that want to print errors (e.g. vet-like tools) would have to traverse the entire import graph to find them. - silence is not the most fail-safe behavior. Change-Id: Ie92b9fb7641ceda429f00928474b650d1dfadedd Reviewed-on: https://go-review.googlesource.com/130576 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.