| commit | e81ad1007af3dfbbc0761df9e1a7ace49b7fd7d2 | [log] [tgz] |
|---|---|---|
| author | Oleksandr Redko <oleksandr.red+github@gmail.com> | Fri Jun 02 21:12:43 2023 +0300 |
| committer | Gopher Robot <gobot@golang.org> | Mon Jun 05 14:39:58 2023 +0000 |
| tree | 696071610cf5a81f70a1d8f5e22c7ca56b32090f | |
| parent | e343115d42363d625a8424d854065a547fe86f5c [diff] |
sumdb: correct spelling mistakes Change-Id: Idb3276b201dbce094201fc5824a1e151f4f71ce8 Reviewed-on: https://go-review.googlesource.com/c/mod/+/500456 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: 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.