| commit | aac77cd49169eebad03b7acf605de172eea0c09a | [log] [tgz] |
|---|---|---|
| author | cui fliter <imcusg@gmail.com> | Tue Oct 11 15:26:15 2022 +0800 |
| committer | Gopher Robot <gobot@golang.org> | Wed Oct 12 13:46:37 2022 +0000 |
| tree | dd0168bbef580e0f92c9fc029f9b1e701c010a92 | |
| parent | 2666ed6287c1b96924b52a1c8402191b853df86d [diff] |
all: fix a few function names on comments Change-Id: I71ed5ce987e5746c27b536c4ac4b43c81099b843 Reviewed-on: https://go-review.googlesource.com/c/mod/+/442075 Reviewed-by: Ian Lance Taylor <iant@google.com> Auto-Submit: Ian Lance Taylor <iant@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Joedian Reid <joedian@golang.org> Run-TryBot: Ian Lance Taylor <iant@google.com>
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.