trouble with package name clashes

[Petar Maymounkov]

I have a project which has a package named "math". While
my package does not collide with Go's math at import, because

import (
a "math"
b "project/math"
)

is ok, a problem occurs in the .go files implementing my math package.
They use Go's math, and so they have to start like this:

package math

import "math"

which causes a compiler error "package cannot import itself".

Does anyone have an elegant work-around? I suppose I am
trying to avoid re-basing the Go library, which would
result in using a non-standard install of Go. This is probably
not a desirable feature to persist.

Thanks,
--Petar

[peterGo]

Petar

import "math" is the same as import math "math", which I would expect
to fail in package math. The problem I have is that the following
fails too.

package math

import gomath "math"

func main() {
const pi = gomath.Pi
}

Peter

[Russ Cox]

Does anyone have an elegant work-around? I suppose I am
trying to avoid re-basing the Go library, which would
result in using a non-standard install of Go. This is probably
not a desirable feature to persist.

For now, there is no elegant work-around.  You have to name

your package something other than math if you need to link

the standard math into your program.  That is, in a single program

all the package names (not just import paths) must be unique.

We plan to eliminate this restriction in the next month or so.

Russ