| commit | ed83ed61efb973124a2a93983ae1ff1431207a45 | [log] [tgz] |
|---|---|---|
| author | Abirdcfly <fp544037857@gmail.com> | Wed Aug 17 10:03:48 2022 +0000 |
| committer | Gopher Robot <gobot@golang.org> | Thu Aug 18 02:21:19 2022 +0000 |
| tree | e3c873a896775d9781d4bfb28f4127e063d5fe7a | |
| parent | f994a2a1254158be9432f5648355eaa09d3902df [diff] |
modfile: remove duplicate words from comments Change-Id: I47505523c97b30648f8be18fed057a6f139e6a00 GitHub-Last-Rev: c3a270cae8af3b25810959b721105c56bba9a974 GitHub-Pull-Request: golang/mod#9 Reviewed-on: https://go-review.googlesource.com/c/mod/+/424454 Auto-Submit: Bryan Mills <bcmills@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: hopehook <hopehook@qq.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@google.com> Run-TryBot: hopehook <hopehook@qq.com> Run-TryBot: Bryan Mills <bcmills@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.