code review 6858049: spec: be clearer about the scope of a package name

spec: be clearer about the scope of a package name

We have the notion of a PackageName, not package identifier.
As is, it could construed that imports that rename a package
don't have an "imported package identifier" but a local one.

[gri, 2012-11-21 02:40:17]

Hello r@golang.org, rsc@golang.org, iant@golang.org, ken@golang.org (cc:
golang-dev@googlegroups.com),

I'd like you to review this change to
https://code.google.com/p/go

[dsymonds, 2012-11-21 03:38:44]

Perhaps "The scope of the package name of an imported package ..." (a
-> the) since an imported package only has one package name?

[gri, 2012-11-21 18:15:51]

PTAL.

http://codereview.appspot.com/6858049/

- gri

On Tue, Nov 20, 2012 at 7:38 PM, David Symonds <dsymonds@golang.org> wrote:
> Perhaps "The scope of the package name of an imported package ..." (a
> -> the) since an imported package only has one package name?

[r, 2012-11-21 19:19:03]

LGTM

[rsc, 2012-11-21 19:29:14]

LGTM

[iant, 2012-11-21 19:46:19]

LGTM

[gri, 2012-11-21 22:40:57]

*** Submitted as http://code.google.com/p/go/source/detail?r=f2755950769b ***

spec: be clearer about the scope of a package name

We have the notion of a PackageName, not package identifier.
As is, it could construed that imports that rename a package
don't have an "imported package identifier" but a local one.

R=r, rsc, iant, ken, dsymonds
CC=golang-dev
http://codereview.appspot.com/6858049