2. Boost Json Translation (zh_Hans)
3. English
4. Zen

18 :42
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_stack>> 19/10000 · 19
19 :23
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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/10000 · 165
19 :184
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 248/10000 · 248
19 :65
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Methodology 11/10000 · 11
19 :78
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Value Type: https://github.com/Tencent/rapidjson/blob/bb5f966b9939d6cdfbac3462a0410e185099b3af/include/rapidjson/document.h#L608[`rapidjson::GenericValue`] 155/10000 · 155
:95 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_array>> 13/10000 · 13
19 :49
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `size_type` parameters that specify a substring, or 51/10000 · 51
19 :123
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 277/10000 · 277
19 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Users can freely combine types with custom conversions with types with library-provided conversions. The library handles them correctly: 136/10000 · 136
19 :61
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Type satisfying <<ref_is_null_like>> 36/10000 · 36
19 :49
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A customization point allowing a memory resource type to indicate that calls 76/10000 · 76
19 :114
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `T` is not a class template 27/10000 · 27
19 :42
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A low level building block used for efficiently building a <<ref_value>>. The 77/10000 · 77
20 :23
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https://ci.appveyor.com/[Appveyor] 34/10000 · 34
20 :190
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Serializing 11/10000 · 11
20 :66
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The input files are all loaded first. Then each configuration is run for a sufficient number of trials to last at least 5 seconds. The elapsed time, number of invocations (of parse or serialize), and bytes transferred are emitted as a sample along with a calculation of throughput expressed in megabytes per second. Several samples (currently five) are generated for each configuration. All but the median two samples are discarded, with the remaining samples averaged to produce a single number which is reported as the benchmark result. 538/10000 · 538
20 :93
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — {icon_bad} The value type is not regular. Assignment is destructive, 68/10000 · 68
20 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_emplace_array>> 27/10000 · 27
20 :50
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — a `const_pointer` parameter, or 31/10000 · 31
20 :128
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 462/10000 · 462