| commit | e343115d42363d625a8424d854065a547fe86f5c | [log] [tgz] |
|---|---|---|
| author | Oleksandr Redko <oleksandr.red+github@gmail.com> | Fri Jun 02 21:06:51 2023 +0300 |
| committer | Gopher Robot <gobot@golang.org> | Fri Jun 02 18:23:18 2023 +0000 |
| tree | d8b58c5e5875944e7184450f6baa5648187da35a | |
| parent | fc83a8faf9931f09514a196d1b7ff229c8efedc6 [diff] |
sumdb: add missing return after http.Error Change-Id: Ic0a9149713f7981e44629b2d96cf2a6ec52d6976 Reviewed-on: https://go-review.googlesource.com/c/mod/+/500455 Reviewed-by: Bryan Mills <bcmills@google.com> Auto-Submit: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Michael Knyszek <mknyszek@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.