From 508bfda6d3dd40e2906fb6538b5e4db0ba129645 Mon Sep 17 00:00:00 2001 From: Russ Cox Date: Sat, 1 Sep 2012 10:34:58 -0400 Subject: [PATCH] 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 --- src/cmd/go/pkg.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cmd/go/pkg.go b/src/cmd/go/pkg.go index 62533b3e018..c9c4e2d779b 100644 --- a/src/cmd/go/pkg.go +++ b/src/cmd/go/pkg.go @@ -250,7 +250,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