| commit | 4435ecfe48157829360bef066e718351d7ef7ba0 | [log] [tgz] |
|---|---|---|
| author | Bryan C. Mills <bcmills@google.com> | Sun May 02 09:17:39 2021 -0400 |
| committer | Bryan C. Mills <bcmills@google.com> | Mon May 03 18:30:26 2021 +0000 |
| tree | fcd5eb8731e2bd6f90a08afa10629738f21561b1 | |
| parent | 858fdbee9c245c8109c359106e89c6b8d321f19c [diff] |
go.mod: upgrade to go 1.17 This change was produced using 'go mod tidy -go=1.17' with a go command built at CL 315210. This activates lazy loading, and updates the go.mod file to maintain the lazy-loading invariants (namely, including an explicit requirement for every package transitively imported by the main module). Note that this does *not* prevent users with earlier go versions from successfully building packages from this module. For golang/go#36460 Change-Id: If672eca0dad61b3f6050a94c758d605b6586cbc3 Reviewed-on: https://go-review.googlesource.com/c/mod/+/316113 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Michael Matloob <matloob@golang.org>
This repository holds packages for writing tools that work directly with Go module mechanics. That is, it is for direct manipulation of Go modules themselves.
It is NOT about supporting general development tools that need to do things like load packages in module mode. That use case, where modules are incidental rather than the focus, should remain in x/tools, specifically x/tools/go/packages.
The specific case of loading packages should still be done by invoking the go command, which remains the single point of truth for package loading algorithms.