Exit Zen
19
:23
English
https://github.com/boostorg/json/actions?query=workflow%3Afuzz+branch%3Adevelop[image:https://github.com/boostorg/json/workflows/fuzz/badge.svg?branch=develop[fuzz]]
165/1650 · 165
19
:49
English
`size_type` parameters that specify a substring, or
28/510 · 51
19
:123
English
As was shown previously, generic conversions provided by the library forward contexts to conversions of nested objects. And in the case when you want to provide your own conversion function for a composite type enabled by a particular context, you usually also need to do that.
72/2770 · 277
19
:95
English
Users can freely combine types with custom conversions with types with library-provided conversions. The library handles them correctly:
43/1360 · 136
:95
:95
English
<<ref_array>>
31/130 · 13
19
:49
English
A customization point allowing a memory resource type to indicate that calls
18/760 · 76
19
:114
English
`T` is not a class template
8/270 · 27
19
:42
English
A low level building block used for efficiently building a <<ref_value>>. The
48/770 · 77
19
:184
English
With strategic use of the right memory resources, parser instance, and calculated upper limits on buffer sizes, it is possible to parse and examine JSON without __any__ dynamic memory allocations. This is explored in more detail in a later section.
78/2480 · 248
19
:65
English
Methodology
3/110 · 11
19
:78
English
Value Type: https://github.com/Tencent/rapidjson/blob/bb5f966b9939d6cdfbac3462a0410e185099b3af/include/rapidjson/document.h#L608[`rapidjson::GenericValue`]
147/1550 · 155
19
:61
English
Type satisfying <<ref_is_null_like>>
52/360 · 36
20
:23
English
https://ci.appveyor.com/[Appveyor]
34/340 · 34
20
:50
English
a `const_pointer` parameter, or
21/310 · 31
20
:128
English
Consider this example. As was discussed in a previous section, <<ref_is_map_like>> requires that your key type satisfies <<ref_is_string_like>>. Now, let's say your keys are not string-like, but they do convert to <<ref_string>>. You can make such maps to also convert to objects using a context. But if you want to also use another context for values, you need a way to pass the full combined context to map elements. So, you want the following test to succeed.
252/4620 · 462
20
:95
English
<<ref_value_emplace_array>>
59/270 · 27
20
:51
English
to deallocate are trivial.
19/260 · 26
20
:115
English
`T` references a {ref_memory_resource}
29/380 · 38
20
:44
English
parsers use this internally, and users may use it to adapt foreign parsers to produce this library's containers. |===
39/1170 · 117
20
:190
English
Serializing
3/110 · 11