Exit Zen
4
:22
English
and removals.
4/130 · 13
5
:24
English
The order of insertions is preserved, as long as there are no removals.
19/710 · 71
6
:26
English
All inserted values will use the same {ref_memory_resource} as the container
40/760 · 76
7
:27
English
itself.
6/100 · 7
8
:29
English
An empty object may be constructed without incurring any memory allocations using the <<default_memory_resource,default memory resource>>. A <<ref_storage_ptr>> can also be explicitly specified:
175/1940 · 194
9
:38
English
Initializer lists consisting of two-element key value pairs can be used to construct objects with initial contents. These constructors may allocate memory and throw:
49/1650 · 165
10
:47
English
Alternatively, elements may be inserted after construction:
17/590 · 59
11
:54
English
Similar to the `std` counterpart, elements may be accessed directly by their key with bounds checking using <<ref_object_at>>, or without bounds checking using <<ref_object_operator_lb_rb>> which creates a null element if the key does not already exist:
165/2530 · 253
12
:64
English
Internally, the container computes a hash table over the keys so that the complexity of lookups is in constant time, on average.
41/1280 · 128
13
:83
English
For the complete listing of all available member functions and nested types, see the reference page for <<ref_object>>.
66/1190 · 119
14
:86
English
As with `std::pair`, the <<ref_key_value_pair>> type can be used with structured bindings in {cpp}17. Specializations of `std::tuple_size`, `std::tuple_element`, and overloads of <<ref_get>> are all provided for this purpose.
172/2250 · 225
15
:91
English
Formatted Output
5/160 · 16
16
:93
English
When an <<ref_object>> is formatted to a {std_ostream}, the result is a valid JSON. That is, the object will be output with curly braces and a comma separated list of key/value pairs, as per the JSON specification.
109/2140 · 214
The translation has come to an end.