I'm not sure what you mean. The name binding created is whatever `package <...>` is in the target package's file, which can be anything.

Ah got it. I think there’s such a strong convention there, that it would be exceedingly rare to see in pratice. It’s probably allowed just for compat reasons at this point — but I think your point is don’t make that mistake in the first place, not that Go is filled with flagrant violations of the convention.