Exit Zen
55
:172
English
The containers <<ref_array>>, <<ref_object>>, and <<ref_value>> all propagate the memory resource they were constructed with to child elements:
127/1430 · 143
56
:133
English
clang: 3.5, 3.6, 3.7, 3.8, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14
63/630 · 63
56
:221
English
After default construction, or after <<ref_stream_parser_reset>> is called with no arguments, the <<ref_value>> produced after a successful parse operation uses the default memory resource. To use a different memory resource, call `reset` with the resource to use. Here we use a <<ref_monotonic_resource>>, which is optimized for parsing but not subsequent modification:
249/3700 · 370
56
:130
English
Here, the map is converted into an <<ref_object>>, since it matches <<ref_is_map_like>>. Each of its keys is converted into a <<ref_string>>, as `std::string` matches <<ref_is_string_like>>, and each of its values is converted into an <<ref_array>>, as `std::pair` matches <<ref_is_tuple_like>>. Finally, elements of pairs are converted into a `std::int64_t` number and a `bool`.
408/3790 · 379
57
:134
English
gcc: 4.8, 4.9, 5, 6, 7, 8, 9, 10, 11, 12
40/400 · 40
57
:90
English
499KB
5/100 · 5
57
:137
English
:leveloffset: +1
16/160 · 16
58
:135
English
msvc: 14.0, 14.1, 14.2, 14.3
28/280 · 28
58
:185
English
It is important to note that <<ref_storage_ptr>> supports both shared-ownership and reference lifetime models. Construction from a memory resource pointer does not transfer ownership:
88/1830 · 183
58
:139
English
include::custom.adoc[] include::nothrow.adoc[] include::alloc.adoc[] include::context.adoc[] include::forward.adoc[] include::direct.adoc[] include::guidelines.adoc[]
166/1660 · 166
59
:95
English
https://en.cppreference.com/w/cpp/language/types[`double`]
58/580 · 58
59
:147
English
:leveloffset: -1
16/160 · 16
60
:200
English
Shared ownership is achieved using the function <<ref_make_shared_resource>>, which creates a new, reference-counted memory resource using a dynamic memory allocation and returns it as a <<ref_storage_ptr>>:
160/2070 · 207
60
:90
English
617KB
5/100 · 5
61
:260
English
Users who wish to implement custom parsing strategies may create their own handler to use with an instance of <<ref_basic_parser>>. The handler implements the function signatures required by SAX event interface. In <<examples_validate>> example we define the "null" parser, which throws out the parsed results, to use in the implementation of a function that determines if a JSON text is valid.
231/3940 · 394
63
:90
English
550KB
5/100 · 5
67
:95
English
https://en.cppreference.com/w/cpp/language/types[`bool`]
56/560 · 56
67
:135
English
521KB
5/100 · 5
69
:140
English
Hardware used for testing: **Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz**, Windows 10, 32GB RAM.
76/940 · 94
73
:149
English
image::images/parse_apache_builds.png[width=668,align="left"]
61/610 · 61