Exit Zen
5
:36
English
Comment
7/100 · 7
6
:4
English
https://vinniefalco.visualstudio.com/json/_build/latest?definitionId=5&branchName=master[image:https://img.shields.io/azure-devops/build/vinniefalco/2571d415-8cc8-4120-a762-c03a8eda0659/8/master[Build
201/2000 · 200
6
:23
English
access. The interface and performance characteristics are similar to {std_vector}.
25/820 · 82
6
:23
English
redundant overloads for string operations have been replaced
13/600 · 60
6
:64
English
When parsing a JSON document, the type used to represent a number is not explicitly specified and must be determined from its value. In general, the parser will choose the best type which can accurately store the number as it appears in the document. Integers (i.e. numbers without decimals or exponents) that cannot be represented by `std::uint64_t` and `std::int64_t` will be represented as `double` to preserve their magnitude:
156/4300 · 430
6
:37
English
Finally, it is worth mentioning that due to the ability to provide conversions to JSON containers without a binary dependency on the library, you don't have to push such dependency on your users. This is particularly relevant for libraries for which interoperation with Boost.JSON is only ancillary.
99/2990 · 299
6
:47
English
Normally, you wouldn't be able to provide conversions for types from third-party libraries and standard types, because it would require yout to put `tag_invoke` overloads into namespaces you do not control. But with contexts you can put the overloads into your namespaces. This is because the context will add its associated namespaces into the list of namespaces where `tag_invoke` overloads are searched.
131/4060 · 406
6
:45
English
`tag_invoke` Overloads
14/220 · 22
6
:42
English
Direct serialization doesn't require any special components and works with the regular <<ref_serializer>> and <<ref_serialize>>.
107/1280 · 128
6
:26
English
All inserted values will use the same {ref_memory_resource} as the container
40/760 · 76
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