Exit Zen
10
:27
English
<<ref_object>>, or <<ref_string>>.
70/340 · 34
10
:36
English
Boost.JSON container.
13/210 · 21
11
:28
English
small strings.
6/140 · 14
11
:59
English
template such as `value_to_tag<T>`) so that its http://eel.is/c++draft/basic.lookup.argdep#2[associated namespaces and entities] are examined when name lookup is performed.
103/1720 · 172
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
11
:100
English
In all cases, the <<ref_storage_ptr>> owned by an <<ref_object>>, <<ref_array>>, or <<ref_value>> constructed from an initializer list will be propagated to each element, recursively.
180/1830 · 183
12
:30
English
With augmented interface, operations requiring an input string are implemented as a single overload with a parameter of type <<ref_string_view>>, and can accept most string-like objects. Objects such as null terminated character pointers, `std::string`, <<ref_string>>, subranges of strings, and objects convertible to <<ref_string_view>> can all be passed to these functions.
229/3760 · 376
12
:38
English
A <<ref_value>> constructed from `nullptr` or default constructed represents a null JSON element:
64/970 · 97
12
:129
English
Up until now we have shown how values may be constructed from a memory resource pointer, where ownership is not transferred. In this case the caller is responsible for ensuring that the lifetime of the resource is extended for the life of the container. Sometimes you want the container to acquire shared ownership of the resource. This is accomplished with <<ref_make_shared_resource>>:
144/3870 · 387
12
:36
English
`bool`
8/100 · 6
13
:66
English
Overloads of `tag_invoke` called by <<ref_value_from>> take the form:
69/690 · 69
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
13
:46
English
The member function <<ref_value_kind,`value::kind`>> may be used to query the kind stored in the value. Alternatively, member functions like <<ref_value_is_object,`value::is_object`>> <<ref_value_is_number,`value::is_number`>> may be used to check whether or not the value is a particular kind:
293/2940 · 294
14
:36
English
A special variant which can hold one of any of the six standard JSON data
34/730 · 73
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
14
:57
English
Functions like <<ref_value_if_object,`value::if_object`>> actually return a pointer to the object if the value is an object, otherwise they return null. This allows them to be used both in boolean contexts as above, and in assignments or conditional expressions to capture the value of the pointer:
161/2980 · 298
14
:35
English
of JSON texts each contained in a single contiguous character buffer, returning each result as a <<ref_value>>.
74/1110 · 111
15
:72
English
While overloads of `tag_invoke` called by <<ref_value_to>> take the form:
65/730 · 73
15
:67
English
After a <<ref_value>> is constructed, its kind can change depending on what is assigned to it, or by calling functions such as <<ref_value_emplace_array,`value::emplace_array`>> or <<ref_value_emplace_bool,`value::emplace_bool`>>. If the assignment is successful, in other words it completes without any exceptions then the value is replaced. Otherwise, the value is unchanged. All operations which can fail to modify a value offer the strong exception safety guarantee.
326/4700 · 470
15
:42
English
The <<ref_serialize>> function converts a <<ref_value>> into a {std_string}:
95/760 · 76