| commit | d6ab96f2441f9631f81862375ef66782fc4a9c12 | [log] [tgz] |
|---|---|---|
| author | Bryan C. Mills <bcmills@google.com> | Tue Mar 09 11:56:07 2021 -0500 |
| committer | Bryan C. Mills <bcmills@google.com> | Tue Mar 09 22:22:12 2021 +0000 |
| tree | db44a21a6f5f3f3741b54410cd76a0d19e87ff0c | |
| parent | c8bb1bd8a2aaa5c50fa106c8116850d503792d16 [diff] |
module: allow '+' in package import paths (but not module paths) For golang/go#44776. Change-Id: I1bc3df2800a1765296c5164aa8bece495d8f9221 Reviewed-on: https://go-review.googlesource.com/c/mod/+/300149 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@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.