qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-22 15:24:42 -07:00
Code Releases Activity

spec: define notion of named type

Browse Source 
The notion of a named type is crucial for the definition
of type identity, assignability, definitions of methods.
Explicitly introduce the notion with an extra sentence.

Fixes #5682.

R=r, rsc, iant
CC=golang-dev
https://golang.org/cl/11055043
This commit is contained in:
Robert Griesemer 2013-07-09 21:12:53 -07:00
parent d178c016c2
commit 8268eadb9e
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/go_spec.html
View File

@ -1,6 +1,6 @@
<!--{ <!--{
"Title": "The Go Programming Language Specification", "Title": "The Go Programming Language Specification",
"Subtitle": "Version of June 21, 2013", "Subtitle": "Version of July 9, 2013",
"Path": "/ref/spec" "Path": "/ref/spec"
}--> }-->
@ -640,10 +640,10 @@ expressions</a>.
<p> <p>
A type determines the set of values and operations specific to values of that A type determines the set of values and operations specific to values of that
type. A type may be specified by a type. Types may be <i>named</i> or <i>unnamed</i>. Named types are specified
(possibly <a href="#Qualified_identifiers">qualified</a>) by a (possibly <a href="#Qualified_identifiers">qualified</a>)
<a href="#Type_declarations"><i>type name</i></a> or a <i>type literal</i>, <a href="#Type_declarations"><i>type name</i></a>; unnamed types are specified
which composes a new type from previously declared types. using a <i>type literal</i>, which composes a new type from existing types.
</p> </p>
<pre class="ebnf"> <pre class="ebnf">
@ -1358,9 +1358,9 @@ Two types are either <i>identical</i> or <i>different</i>.
</p> </p>
<p> <p>
Two named types are identical if their type names originate in the same Two <a href="#Types">named types</a> are identical if their type names originate in the same
<a href="#Type_declarations">TypeSpec</a>. <a href="#Type_declarations">TypeSpec</a>.
A named and an unnamed type are always different. Two unnamed types are identical A named and an <a href="#Types">unnamed type</a> are always different. Two unnamed types are identical
if the corresponding type literals are identical, that is, if they have the same if the corresponding type literals are identical, that is, if they have the same
literal structure and corresponding components have identical types. In detail: literal structure and corresponding components have identical types. In detail:
</p> </p>
@ -1442,7 +1442,7 @@ A value <code>x</code> is <i>assignable</i> to a variable of type <code>T</code>
<li> <li>
<code>x</code>'s type <code>V</code> and <code>T</code> have identical <code>x</code>'s type <code>V</code> and <code>T</code> have identical
<a href="#Types">underlying types</a> and at least one of <code>V</code> <a href="#Types">underlying types</a> and at least one of <code>V</code>
or <code>T</code> is not a named type. or <code>T</code> is not a <a href="#Types">named type</a>.
</li> </li>
<li> <li>
<code>T</code> is an interface type and <code>T</code> is an interface type and