Home | History | Annotate | Download | only in doc

Lines Matching full:composite

638 or taking the address of a <a href="#Composite_literals">composite literal</a>
654 <code>new</code> call or composite literal, or the type of
699 <i>Composite types</i>&mdash;array, struct, pointer, function,
1023 <a href="#Composite_literals">composite literals</a> of the struct.
1990 of an interface type or of elements of a composite type remains unchanged:
2317 <h3 id="Composite_literals">Composite literals</h3>
2320 Composite literals construct values for structs, arrays, slices, and maps
2413 <a href="#Address_operators">Taking the address</a> of a composite literal
2456 Within a composite literal of array, slice, or map type <code>T</code>,
2457 elements or map keys that are themselves composite literals may elide the respective
2459 Similarly, elements or keys that are addresses of composite literals may elide
2476 A parsing ambiguity arises when a composite literal using the
2479 of an "if", "for", or "switch" statement, and the composite literal
2483 the composite literal must appear within parentheses.
3841 <a href="#Composite_literals">composite literal</a>.
6202 a new value is created, either through a composite literal or a call