Hi pudds,
I’ve run go mod verify multiple times on my laptop for the same module. The
elapsed time for the command to run is always 25 seconds or thereabouts. So
I figured that whatever caching might be there, I would be getting it.
I can try this with go mod vendor and see if that helps but I’d
Hi Joe,
Sorry, I realized I pasted in the wrong quote from the documentation.
I meant to include this quote instead
(from https://golang.org/cmd/go/#hdr-Module_downloading_and_verification):
"The go command maintains, in the main module's root directory alongside
go.mod, a file named go.sum co
Hi Joe,
As far as I know, I think it is computing the SHA256 of the dependencies:
https://github.com/golang/go/blob/release-branch.go1.11/src/cmd/go/internal/dirhash/hash.go#L25
Personally, I wouldn't expect that to get pathologically worse with more
dependencies.
Also, just as you can often s