Exit Zen
6
:38
English
The overload lets us use `ip_address` with <<ref_try_value_to>>.
76/640 · 64
6
:36
English
This implementation explicitly creates an <<ref_array>> rather than relying on assignment from an initializer list. But the array uses default {ref_memory_resource}, not the one used by `jv`.
108/1910 · 191
6
:29
English
**string**: A sequence of zero or more Unicode characters,
29/580 · 58
6
:52
English
For the complete listing of all available member functions and nested types, see the reference page for <<ref_array>>.
63/1180 · 118
6
:24
English
Storage pointers constructed from a {ref_memory_resource} or
33/600 · 60
6
:26
English
"Why use <<ref_storage_ptr>> over {ref_polymorphic_allocator}?:: {ref_polymorphic_allocator} treats the memory resource as a reference with respect to ownership. Boost.JSON uses a reference counted smart pointer container to simplify the lifetime management of memory resources. In addition to being reference counted, <<ref_storage_ptr>> can function as an uncounted reference wrapper around a {ref_memory_resource}.
260/4170 · 417
6
:39
English
:leveloffset: -1
16/160 · 16
6
:35
English
The system of allocator traits, especially POCCA and POCMA,
26/590 · 59
6
:55
English
*Operators* +
7/130 · 13
6
:23
English
The member function `get_allocator` returns an instance of
25/580 · 58
6
:23
English
a series of member function calls to a user provided handler. This allows custom behaviors to be implemented for representing the document in memory.
38/1490 · 149
6
:76
English
While keys are strings, the mapped type of objects and the element type of arrays is the aforementioned type <<ref_value>> which can hold any JSON element, as seen in the previous assignments. Instead of building the JSON document using a series of function calls, we can build it in one statement using an initializer list:
135/3240 · 324
6
:26
English
which is optimized for parsing without subsequent modification. The <<ref_stream_parser>> object is reused between trials, allowing temporary memory allocated by the implementation to persist and improve performance.
109/2160 · 216
6
:50
English
This library adopts a "kitchen sink" approach. It contains a wealth of features, even those with niche uses. Its weakness is that the many template parameters, while allowing for configurability, inhibit the best possible optimizations. The consequence is that the library performs poorly. The ability to configure every aspect of the value type has the paradoxical effect of making it less suitable as a vocabulary type.
153/4210 · 421
6
:18
English
Serialize a <<ref_value>>, <<ref_array>>, <<ref_object>>, or <<ref_string>>
139/750 · 75
6
:52
English
To resolve the ambiguity manually, use an explicit constructor:
18/630 · 63
6
:36
English
`value_from` behavior
21/210 · 21
7
:9
English
Status]] |https://vinniefalco.visualstudio.com/json/_build/latest?definitionId=8&branchName=develop[image:https://img.shields.io/azure-devops/build/vinniefalco/2571d415-8cc8-4120-a762-c03a8eda0659/8/develop[Build Status]]
221/2210 · 221
7
:26
English
<<ref_object>>
33/140 · 14
7
:24
English
with a <<ref_string_view>>-based interface,
54/430 · 43