mirror
/
go
mirror of https://github.com/golang/go.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

spec: tighten the wording around . imports 

Make it clear that if you do a . import, you cannot use a qualified identifier.

R=gri
CC=golang-codereviews
https://golang.org/cl/52390043
This commit is contained in:
Rob Pike 2014-01-14 15:16:01 -08:00
parent 591265fcb4
commit 227fe5f64e
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/go_spec.html
View File

@ -1,6 +1,6 @@
<!--{
"Title": "The Go Programming Language Specification",
"Subtitle": "Version of Jan 2, 2014",
"Subtitle": "Version of Jan 14, 2014",
"Path": "/ref/spec"
}-->
@ -5669,7 +5669,7 @@ If the PackageName is omitted, it defaults to the identifier specified in the
If an explicit period (<code>.</code>) appears instead of a name, all the
package's exported identifiers declared in that package's
<a href="#Blocks">package block</a> will be declared in the importing source
file's file block and can be accessed without a qualifier.
file's file block and must be accessed without a qualifier.
</p>
<p>
@ -5693,7 +5693,7 @@ Assume we have compiled a package containing the package clause
<code>package math</code>, which exports function <code>Sin</code>, and
installed the compiled package in the file identified by
<code>"lib/math"</code>.
This table illustrates how <code>Sin</code> may be accessed in files
This table illustrates how <code>Sin</code> is accessed in files
that import the package after the
various types of import declaration.
</p>