Exit Zen
8
:55
English
discard candidates that are unrelated to that particular
18/560 · 56
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
:32
English
**array**: An ordered list of values, like {std_vector}.
30/560 · 56
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
:29
English
A storage pointer obtained from <<ref_make_shared_resource>> acquires shared
75/760 · 76
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
:38
English
Allocator-based programs which use multiple allocator types incur a greater number of function template instantiations and are generally slower to compile because class template function definitions must be visible at all call sites.
63/2330 · 233
8
:64
English
*Aliases* + <<ref_parser_for>> + <<ref_string_view>>
94/520 · 52
8
:27
English
Practically, this means that when a library container type is used in a standard container that uses a polymorphic allocator, the allocator will propagate to the JSON type. For example:
54/1850 · 185
8
:26
English
A structure used to select which extensions are enabled during parsing.
21/710 · 71
8
:99
English
Allocators
3/100 · 10
8
:32
English
Parses the input using the <<default_memory_resource, default memory
20/680 · 68
8
:58
English
choices of template parameters to be interoperable.
23/510 · 51
8
:25
English
<<ref_serialize>>
39/170 · 17
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
8
:36
English
Custom conversion.
6/180 · 18
9
:13
English
https://www.boost.org/doc/libs/master/libs/json/[image:https://img.shields.io/badge/docs-master-brightgreen.svg[Documentation]]
116/1270 · 127
9
:28
English
is a string and the mapped type is a JSON value. Search, insertion, and removal have average contant-time complexity. In addition, elements are stored contiguously in memory allowing cache-friendly iteration.
63/2080 · 208
9
:26
English
<<ref_storage_ptr>> is used instead of {req_Allocator}, and
64/590 · 59