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

18 :58
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https://nlohmann.github.io/json/classnlohmann_1_1basic__json_ab330c13ba254ea41fbc1c52c5c610f45.html[`json::parse`], which uses the default `std` allocator, and is designed for general use including mutation of the document after it is parsed. This library does not provide an interface to reuse temporary storage used during parsing or serialization on subsequent operations. |=== 380/10000 · 380
18 :76
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Comparison to RapidJSON 23/10000 · 23
:95 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_kind,`kind::array`>> 26/10000 · 26
18 :48
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — a parameter of a type convertible to <<ref_string_view>> and two 64/10000 · 64
18 :122
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Contexts and Composite Types 28/10000 · 28
18 :86
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Since the type being converted is embedded into the function's signature, user-provided overloads are visible to argument-dependent lookup and will be candidates when a conversion is performed: 193/10000 · 193
18 :61
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The result is created via <<ref_value_to_number>>. 50/10000 · 50
18 :49
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_is_deallocate_trivial>> 29/10000 · 29
18 :111
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — We would like an allocator model using a single type `T` with the following properties: 87/10000 · 87
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