| commit | 69aa7acea306dfd277ec48fcc687ef8fa0f2bdb4 | [log] [tgz] |
|---|---|---|
| author | hickford <hickford@google.com> | Thu Feb 23 10:57:05 2023 +0000 |
| committer | Gopher Robot <gobot@golang.org> | Mon Feb 27 21:59:11 2023 +0000 |
| tree | 8693bf7e6338aa79495061ff10bc80ca91091428 | |
| parent | b71060237c896c7c9fc602ab66e33ea6079659fa [diff] |
sumdb/tlog: fuzz tests for parsers Future fuzz tests could test round trip properties Change-Id: If195b82998ebedaeca68a7723c2558369e68f716 GitHub-Last-Rev: 6fff4e678380610ecb5f34e494cec04a9a462f62 GitHub-Pull-Request: golang/mod#18 Reviewed-on: https://go-review.googlesource.com/c/mod/+/470155 Run-TryBot: Matthew Hickford <hickford@google.com> Auto-Submit: Bryan Mills <bcmills@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Matthew Hickford <hickford@google.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.