Heschi Kreinick d2fffb4b84 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>		2019-10-21 20:45:41 +00:00
..
walk_test.go	internal/imports: skip scanned module cache dirs	2019-08-29 21:03:13 +00:00
walk.go	internal/imports: cache things outside the mod cache	2019-10-21 20:45:41 +00:00