Exit Zen
26
:61
English
The result is constructed from a <<ref_string_view>>.
51/530 · 53
27
:94
English
When building with {cpp}20 or later, the use of https://en.cppreference.com/w/cpp/language/aggregate_initialization#Designated_initializers[designated initializers] with <<ref_parse_options>> is possible:
176/2040 · 204
27
:61
English
Type satisfying <<ref_is_variant_like>>.
59/400 · 40
28
:88
English
When a <<ref_string>> is formatted to a {std_ostream}, the result is a valid JSON. That is, the result will be double quoted and the contents properly escaped per the JSON specification.
101/1860 · 186
28
:243
English
To go from JSON to a user-defined type we use <<ref_value_to>>, which uses another overload of `tag_invoke`. This converts a JSON value to a `customer`. It throws an exception if the contents of the value do not match what is expected:
129/2350 · 235
29
:108
English
{icon_good} Parsing and serialization performance is better than most other
28/750 · 75
29
:61
English
The result is equal to the result of conversion of the active variant
24/690 · 69
30
:94
English
<<ref_string>> directly supports access to its storage in the range `[size(), capacity())`. This can be used for efficient assembly of a string from several parts. After the string is assembled, use the member function <<ref_string_grow>> to update the string's size and insert the null terminator. For example:
175/3110 · 311
30
:114
English
when reading the input. For example, `std::getline` removes the endline characters from the string it produces.
40/1110 · 111
30
:78
English
The largest file, containing a large number of 2-element arrays holding
15/710 · 71
30
:76
English
alternative. |The result holds the first alternative for which a conversion succeeds.
21/850 · 85
31
:270
English
The library's generic algorithms recognize when you are converting a <<ref_value>> to a container which resembles an array or object, so if you wanted to turn a JSON array into a vector of customers you might write:
91/2150 · 215
31
:88
English
floating-point coordinate pairs.
19/320 · 32
32
:118
English
The default algorithm that the library uses to parse numbers is fast, but may result in slight precision loss. This may not be suitable for some applications, so there is an option to enable an alternative algorithm that doesn't have that flaw, but is somewhat slower. To do this, you also need to use <<ref_parse_options>> structure.
130/3340 · 334
33
:129
English
Note that full precision number parsing requires the algorithm to see the full number. This means, that when used with <<ref_stream_parser>>, additional memory allocations may be necessary to store the number parts which were so far accepted by the parser. The library does try its best to avoid such allocations.
123/3130 · 313
34
:87
English
Type satisfying <<ref_is_map_like>>.
60/360 · 36
35
:136
English
Instances of <<ref_parser>> and <<ref_stream_parser>> offer functionality beyond what is available when using the <<ref_parse>> free functions:
142/1430 · 143
36
:87
English
The result is an <<ref_object>>.
51/320 · 32
38
:87
English
Type satisfying <<ref_is_sequence_like>>.
70/410 · 41
39
:85
English
Visit https://boost.org/libs/json for complete documentation.
44/610 · 61