mirror of https://github.com/golang/go.git
60da08ac03
The memoize cache buys us little for files: the cache value is not really a function of the inputs, but rather the filesystem state. It's pretty much just as easy to manage them explicitly, and it's a start at simplifying our caching strategy. We do lose one small feature: if we try to read the same file concurrently, reads will not be deduplicated. I suspect that doesn't matter. Change-Id: I75e219467fb7a512d9cfdf87443d012c85f03df9 Reviewed-on: https://go-review.googlesource.com/c/tools/+/243197 Reviewed-by: Rebecca Stambler <rstambler@golang.org> Reviewed-by: Robert Findley <rfindley@google.com> |
||
|---|---|---|
| .. | ||
| analysisinternal | ||
| apidiff | ||
| event | ||
| fakenet | ||
| fastwalk | ||
| gocommand | ||
| gopathwalk | ||
| imports | ||
| jsonrpc2 | ||
| lsp | ||
| memoize | ||
| packagesinternal | ||
| proxydir | ||
| span | ||
| stack | ||
| testenv | ||
| tool | ||
| typesinternal | ||
| xcontext | ||