mirror of
https://github.com/golang/go
synced 2024-11-08 00:26:18 -07:00
68170aa677
If a single module is imported via two different paths (e.g., as itself and as a replacement for something else), some users may be surprised if the two paths do not share the same package-level state. Others may be surprised if the two paths do share state. Punt on the question for now by rejecting that condition explicitly. Fixes #26607. Change-Id: I15c3889f61f8dd4ba5e5c48ca33ad63aeecac04e Reviewed-on: https://go-review.googlesource.com/126156 Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Russ Cox <rsc@golang.org> |
||
---|---|---|
.. | ||
addr2line | ||
api | ||
asm | ||
buildid | ||
cgo | ||
compile | ||
cover | ||
dist | ||
doc | ||
fix | ||
go | ||
gofmt | ||
internal | ||
link | ||
nm | ||
objdump | ||
pack | ||
pprof | ||
test2json | ||
trace | ||
vendor | ||
vet |