|author||Heschi Kreinick <firstname.lastname@example.org>||Tue Nov 05 17:53:32 2019 -0500|
|committer||Rebecca Stambler <email@example.com>||Thu Nov 07 00:06:55 2019 +0000|
internal/imports: set import names on completion candidates I forgot to set .Name on completion candidates. That meant that if the package name didn't match the import path, you'd first get an import without a name, then it would be added when you organized imports. Change-Id: Ic374de872324effa6bc04c1440c659d7a182d17f Reviewed-on: https://go-review.googlesource.com/c/tools/+/205503 Run-TryBot: Heschi Kreinick <firstname.lastname@example.org> Reviewed-by: Rebecca Stambler <email@example.com> TryBot-Result: Gobot Gobot <firstname.lastname@example.org> (cherry picked from commit 689d0f08e67ae0c77c260e137ac6a3729498c92f) Reviewed-on: https://go-review.googlesource.com/c/tools/+/205660 Reviewed-by: Heschi Kreinick <email@example.com>
This subrepository holds the source for various packages and tools that support the Go programming language.
Some of the tools,
vet for example, are included in binary Go distributions.
Others, including the Go
guru and the test coverage tool, can be fetched with
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
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.