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

go spec: adjust notion of Assignability

Browse Source 
This change makes it legal to pass a struct value as receiver
outside the package declaring the struct even if the respective
struct type has non-exported fields.

This is a backwards-compatible language change motivated by the
fact that it is already possible to circumvent the assignment
restriction when calling methods through interfaces (see issue
1402).

R=r, rsc, iant, ken2
CC=golang-dev
https://golang.org/cl/3926044
This commit is contained in:
Robert Griesemer 2011-02-03 10:53:31 -08:00
parent ab15a978fb
commit fa3d0d73f0
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/go_spec.html
View File

@ -1349,11 +1349,12 @@ by a value of type <code>T</code>.
</ul> </ul>
<p> <p>
If <code>T</code> is a struct type, either all fields of <code>T</code> If <code>T</code> is a struct type with non-<a href="#Exported_identifiers">exported</a>
must be <a href="#Exported_identifiers">exported</a>, or the assignment must be in fields, the assignment must be in the same package in which <code>T</code> is declared,
the same package in which <code>T</code> is declared. or <code>x</code> must be the receiver of a method call.
In other words, a struct value can be assigned to a struct variable only if In other words, a struct value can be assigned to a struct variable only if
every field of the struct may be legally assigned individually by the program. every field of the struct may be legally assigned individually by the program,
or if the assignment is initializing the receiver of a method of the struct type.
</p> </p>
<p> <p>