Exit Zen
7
:59
English
Initializer lists can be used to unambiguously construct or assign an <<ref_object>> or <<ref_array>>:
86/1020 · 102
7
:36
English
`value_to` behavior
19/190 · 19
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
8
:52
English
The opposite is also true: if there's a `tag_invoke` overload intended for <<ref_try_value_to>>, but not for <<ref_value_to>>, then calling <<ref_value_to>> will invoke the non-throwing overload, then construct a {ref_system_error} from the {ref_error_code} and throw it. Due to these fallbacks, it is recommended that users provide the overload from this section, rather then the other one, if they ever intend to use <<ref_try_value_to>>.
327/4400 · 440
8
:57
English
When an <<ref_array>> is formatted to a {std_ostream}, the result is a valid JSON. That is, the array will be output with square brackets and the comma separated list of values, as per the JSON specification.
100/2080 · 208
8
:35
English
library uses the <<ref_storage_ptr>> allocator model, has the same interface on all C++ versions, and has an optimized class layout to keep the size of JSON values small. <<ref_string>> also implements an improved interface that replaces extraneous overloads with ones that use <<ref_string_view>>.
201/2980 · 298
8
:67
English
Similarly, an initializer list for an <<ref_object>> is always interpreted as an <<ref_object>>. In such cases, the initializer list must be a list of key-value pairs. For example, the following code will not compile because `1` is not convertible to a string:
133/2600 · 260
9
:100
English
To permit custom memory allocation strategies, these containers all allow construction with a <<ref_storage_ptr>> which is a smart pointer to a {ref_memory_resource}. The constructor signatures have the same ordering as their `std` equivalents which use {req_Allocator} parameters. Once a container is constructed its memory resource can never change. Here we create an array without performing any dynamic allocations:
192/4190 · 419
9
:34
English
resource>>, which uses the standard C++ allocator, and is designed for general use including mutation of the document after it is parsed. The <<ref_stream_parser>> object is reused between trials, allowing temporary memory allocated by the implementation to persist and improve performance.
322/2900 · 290
9
:77
English
The requirement for an initializer list to be interpreted as an <<ref_object>> or <<ref_array>> when initializing such an entity only applies to the outermost initializer list; subsequent nested elements will follow the usual ambiguity resolution rules.
129/2530 · 253
10
:27
English
small buffer optimisation is guaranteed, which avoids allocating memory for
25/750 · 75
10
:39
English
*rapidjson(pool)*
17/170 · 17
10
:27
English
<<ref_object>>, or <<ref_string>>.
70/340 · 34
10
:36
English
Boost.JSON container.
13/210 · 21
11
:13
English
https://drone.io/[Drone]
24/240 · 24
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