| commit | 607370acc07b934e867b267414e276c4bbb2c991 | [log] [tgz] |
|---|---|---|
| author | Tobias Klauser <tklauser@distanz.ch> | Fri Jun 11 13:00:26 2021 +0200 |
| committer | Tobias Klauser <tobias.klauser@gmail.com> | Mon Aug 16 07:22:36 2021 +0000 |
| tree | e924cff60edcefcca770d1040d34138beb2c31af | |
| parent | 98d530ac93a63bbe50476a9e26c85daa42f913ef [diff] |
module: use strings.ContainsRune in fileNameOK As suggested by Ian for similar code on CL 326010. Change-Id: I7c6ca4191481daf253eba5f12e7079f5c3522e88 Reviewed-on: https://go-review.googlesource.com/c/mod/+/327029 Trust: Tobias Klauser <tobias.klauser@gmail.com> Run-TryBot: Tobias Klauser <tobias.klauser@gmail.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Bryan C. 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.