template <typename BuilderImpl>
class WireTableBaseBuilder
Defined at line 4770 of file fidling/gen/sdk/fidl/fuchsia.sysmem2/fuchsia.sysmem2/cpp/fidl/fuchsia.sysmem2/cpp/wire_types.h
Public Methods
::fuchsia_sysmem2::wire::Heap Build ()
Build and return the table. The builder should not be used after this.
bool has_heap_type ()
void clear_heap_type ()
Clears the heap_type field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
::fidl::StringView & heap_type ()
The type of the heap, specified using a bind string defined per the
schema and mechanism described in comments in the
fuchsia.sysmem.heap.bind file.
Examples:
* "fuchsia.sysmem.heap.HEAP_TYPE.SYSTEM_RAM"
* "fuchsia.goldfish.platform.sysmem.heap.HEAP_TYPE.HOST_VISIBLE"
BuilderImpl & heap_type (Wrapper_Ignore_Me_< ::fidl::ObjectView< ::fidl::StringView>> elem)
The type of the heap, specified using a bind string defined per the
schema and mechanism described in comments in the
fuchsia.sysmem.heap.bind file.
Examples:
* "fuchsia.sysmem.heap.HEAP_TYPE.SYSTEM_RAM"
* "fuchsia.goldfish.platform.sysmem.heap.HEAP_TYPE.HOST_VISIBLE"
bool has_id ()
void clear_id ()
Clears the id field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
uint64_t & id ()
The uint64 id of the heap. This is only required to be unique per (type,
boot) tuple. In other words, a given heap id is only meaningful within
the current boot of the machine (not across boots), and only within the
`Heap.type`.
For `Heap.type`(s) that refer to a singleton heap, a participant
specifying the singleton heap in
[`fuchsia.sysmem2.BufferMemoryConstraints.permitted_heaps`] can leave
this field un-set, or set it to zero. Sysmem will always fill out this
field for the heap indicated in
[`fuchsia.sysmem2.BufferMemorySettings.heap`] (for a singleton heap the
`id` field will be set to 0 by sysmem).
BuilderImpl & id (Wrapper_Ignore_Me_< ::fidl::ObjectView<uint64_t>> elem)
The uint64 id of the heap. This is only required to be unique per (type,
boot) tuple. In other words, a given heap id is only meaningful within
the current boot of the machine (not across boots), and only within the
`Heap.type`.
For `Heap.type`(s) that refer to a singleton heap, a participant
specifying the singleton heap in
[`fuchsia.sysmem2.BufferMemoryConstraints.permitted_heaps`] can leave
this field un-set, or set it to zero. Sysmem will always fill out this
field for the heap indicated in
[`fuchsia.sysmem2.BufferMemorySettings.heap`] (for a singleton heap the
`id` field will be set to 0 by sysmem).
Protected Methods
void WireTableBaseBuilder< ::fuchsia_sysmem2::wire::Heap, BuilderImpl> (::fidl::ObjectView< ::fidl::WireTableFrame< ::fuchsia_sysmem2::wire::Heap>> && frame)