| commit | d2fffb4b843bb077b595d8c48cbe19284635caff | [log] [tgz] |
|---|---|---|
| author | Heschi Kreinick <heschi@google.com> | Wed Oct 09 19:05:30 2019 -0400 |
| committer | Heschi Kreinick <heschi@google.com> | Mon Oct 21 20:45:41 2019 +0000 |
| tree | a5192ebe7bc2ca515a2768eb9e001db94ee60a73 | |
| parent | eb46839a9601bca76a241ce34cb6992aa2a1c80b [diff] |
internal/imports: cache things outside the mod cache Since a user's module cache is generally going to be much bigger than their main module, one would expect that caching just information about the module cache would be sufficient. It turns out that's not correct. When we discover something in the module cache, we have to make sure that a different version of it isn't already in scope. Doing that can require information about the main module or replace targets, so that needs to be cached too. Concretely, when I'm working in x/tools, if a scan discovers a version of x/tools in the module cache, it should usually ignore that version. But that might not be true in more complicated cases, especially those involving nested modules whose boundaries change. So, cache everything except GOROOT. Since the new data is mutable, we store it separately from the module cache data so that it can be discarded easily between runs. Change-Id: I47364f6c0270fee03af8898fec6c85d1b9c8d780 Reviewed-on: https://go-review.googlesource.com/c/tools/+/202045 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 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.