| commit | 5517a715a62aaf2d2ab02e64ce67586c60767e8f | [log] [tgz] |
|---|---|---|
| author | cuishuang <imcusg@gmail.com> | Mon Oct 20 18:13:54 2025 +0800 |
| committer | Gopher Robot <gobot@golang.org> | Fri Oct 24 11:41:23 2025 -0700 |
| tree | 9746ae0639b9565686e717161c38c4f9df864252 | |
| parent | b6cdd1a97c6a688a6a842cdc667ec2e68174ba9d [diff] |
all: fix some comments Change-Id: Ic8faee52db43f1c669dbc8d141eeda3c7093bd29 Reviewed-on: https://go-review.googlesource.com/c/mod/+/712901 Auto-Submit: Sean Liao <sean@liao.dev> Reviewed-by: Sean Liao <sean@liao.dev> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: David Chase <drchase@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.