aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRuss Cox <rsc@golang.org>2012-09-22 05:54:56 +1000
committerRuss Cox <rsc@golang.org>2012-09-22 05:54:56 +1000
commite09cf61b6430c03a912d749ced1a79b124c7c0fe (patch)
tree29ef5d2e31b150629fefdd6f95bd9558b64528db
parent42b175477508a2ce3c2febd252a100efef9e1e3e (diff)
downloadgo-e09cf61b6430c03a912d749ced1a79b124c7c0fe.tar.gz
go-e09cf61b6430c03a912d749ced1a79b124c7c0fe.zip
[release-branch.go1] cmd/go: be clear that import loops are bad
««« backport f697709b5082 cmd/go: be clear that import loops are bad There was mail on golang-nuts a few weeks ago from someone who understood the message perfectly and knew he had a cyclic dependency but assumed that Go, like Python or Java, was supposed to handle it. R=golang-dev, bradfitz, dave CC=golang-dev https://golang.org/cl/6488069 »»»
-rw-r--r--src/cmd/go/pkg.go2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/cmd/go/pkg.go b/src/cmd/go/pkg.go
index 30bbfad55a..51046412fc 100644
--- a/src/cmd/go/pkg.go
+++ b/src/cmd/go/pkg.go
@@ -246,7 +246,7 @@ func reusePackage(p *Package, stk *importStack) *Package {
if p.Error == nil {
p.Error = &PackageError{
ImportStack: stk.copy(),
- Err: "import loop",
+ Err: "import cycle not allowed",
}
}
p.Incomplete = true