Training
Module
Use data types and structs, arrays, slices, and maps in Go - Training
Learn about structs, arrays, slices, and maps. Understand the difference between them and when to use one type over the other.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Several array categories have been defined based on their performance characteristics, primarily whether the array can be block-copied.
For some categories, such as a fixed-size array, two types of array descriptors exist; they are indicated by an in-fix in the name of the leading FC token.
Format character | Description |
---|---|
SM | The type's total size can be represented in a 16-bit unsigned int. |
LG | The type's total size needs a 32-bit unsigned long to be represented. |
Fields common to arrays:
total_size
Total size of the array in memory, in bytes. This is the same as wire size after alignment. The total size is calculated for categories for which the padding issue does not exist and the size is actual array size.
element_size
Total size in memory of a single element of the array, including padding (this may happen for complex arrays only).
element_description
Description of the array element type.
pointer_layout
See the Pointer Layout topic for more information.
A fixed-sized array format string is generated for arrays that have a known size, and therefore may be block-copied to the marshaling buffer. The two fixed array descriptor formats are as follows.
FC_SMFARRAY alignment<1>
total_size<2>
[pointer_layout<>]
element_description<>
FC_END
and
FC_LGFARRAY alignment<1>
total_size<4>
[pointer_layout<>]
element_description<>
FC_END
A conformant array can be block-copied once the size of the array is known.
FC_CARRAY alignment<1>
element_size<2>
conformance_description<>
[pointer_layout<>]
element_description<>
FC_END
The conformance_description<> is a correlation descriptor and has 4 or 6 bytes depending on whether /robust is used.
A conformant varying array can also be block-copied.
FC_CVARRAY alignment<1>
element_size<2>
conformance_description<>
variance_description<>
[pointer_layout<>]
element_description<>
FC_END
The conformance_description<> and variance_description<> is a correlation descriptor and has 4 or 6 bytes depending on whether /robust is used.
The varying arrays have two possibilities depending on the size of the array.
FC_SMVARRAY alignment<1>
total_size<2>
number_elements<2>
element_size<2>
variance_description<>
[pointer_layout<>]
element_description<>
FC_END
FC_LGVARRAY alignment<1>
total_size<4>
number_elements<4>
element_size<2>
variance_description<4>
[pointer_layout<>]
element_description<>
FC_END
The variance_description<> is a correlation descriptor and has 4 or 6 bytes depending on the /robust being used.
For varying arrays embedded inside of a structure, the offset<2> field of the variance_description<> is a relative offset from the varying array's position in the structure to the variance describing field. The offset is typically relative to the beginning of the structure.
A complex array is any array with an element that prevents it from being block-copied, and as such, additional action needs to be taken. These elements make an array complex:
The complex array description is as follows:
FC_BOGUS_ARRAY alignment<1>
number_of_elements<2>
conformance_description<>
variance_description<>
element_description<>
FC_END
The number_of_elements<2> field is zero if the array is conformant.
The conformance_description<> and variance_description<> is a correlation descriptor and has 4 or 6 bytes depending on whether /robust is used. If the array has conformance and/or variance then the conformance_description<> and/or variance_description<> field(s) have valid descriptions, otherwise the first 4 bytes of the correlation descriptor are set to 0xFFFFFFFF. The flags, when present, are set to zero.
Training
Module
Use data types and structs, arrays, slices, and maps in Go - Training
Learn about structs, arrays, slices, and maps. Understand the difference between them and when to use one type over the other.