| commit | 154199deab1bd1b6a11f3a0524fa42cf2ca539df | [log] [tgz] |
|---|---|---|
| author | Jean de Klerk <deklerk@google.com> | Fri Jul 30 11:58:01 2021 -0600 |
| committer | Jean de Klerk <deklerk@google.com> | Mon Aug 02 15:30:50 2021 +0000 |
| tree | 443a46e24597b4fa61bd8026e4bffd3637d69865 | |
| parent | 0f08993efd8a8ec67e75bcccf86b0e1569b0ab0a [diff] |
zip: add bit more information about what checkFiles does This CL adds a headstone to checkFiles in the form of additional documentation, which should hopefully help future developers. Change-Id: I7957766fc78da45007cbb4e7e3ed59ad2bada4c5 Reviewed-on: https://go-review.googlesource.com/c/mod/+/338669 Trust: Jean de Klerk <deklerk@google.com> Run-TryBot: Jean de Klerk <deklerk@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Jay Conrod <jayconrod@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.