Commit 369a974b authored by Robert Griesemer's avatar Robert Griesemer

spec: slight wording change to remove a formal contradiction

Fixes #4324.

R=r
CC=golang-dev
https://golang.org/cl/6822062
parent 5176481f
...@@ -2128,18 +2128,18 @@ For struct literals the following rules apply: ...@@ -2128,18 +2128,18 @@ For struct literals the following rules apply:
<ul> <ul>
<li>A key must be a field name declared in the LiteralType. <li>A key must be a field name declared in the LiteralType.
</li> </li>
<li>A literal that does not contain any keys must <li>An element list that does not contain any keys must
list an element for each struct field in the list an element for each struct field in the
order in which the fields are declared. order in which the fields are declared.
</li> </li>
<li>If any element has a key, every element must have a key. <li>If any element has a key, every element must have a key.
</li> </li>
<li>A literal that contains keys does not need to <li>An element list that contains keys does not need to
have an element for each struct field. Omitted fields have an element for each struct field. Omitted fields
get the zero value for that field. get the zero value for that field.
</li> </li>
<li>A literal may omit the element list; such a literal evaluates <li>A literal may omit the element list; such a literal evaluates
to the zero value for its type. to the zero value for its type.
</li> </li>
<li>It is an error to specify an element for a non-exported <li>It is an error to specify an element for a non-exported
field of a struct belonging to a different package. field of a struct belonging to a different package.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment