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

10 :35
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https://en.wikipedia.org/wiki/Associative_array[__associative array__]. 71/10000 · 71
10 :32
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_string>> 14/10000 · 14
10 :27
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — small buffer optimisation is guaranteed, which avoids allocating memory for 75/10000 · 75
10 :80
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — is negative and its value is less than `INT64_MIN`, or 54/10000 · 54
10 :73
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — One particular use case that is enabled by contexts is adaptor libraries that define JSON conversion logic for types from a different library. 142/10000 · 142
10 :58
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — embed the user-defined type into the arguments list (e.g. by using a tag type 77/10000 · 77
10 :36
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Boost.JSON container. 21/10000 · 21
10 :33
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The storage pointer remembers the value of <<ref_is_deallocate_trivial>> 72/10000 · 72
10 :44
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — {cpp}17 improves the allocator model by representing the low-level allocation operation with an abstract interface called {ref_memory_resource}, which is not parameterized on the element type, and has no traits: 211/10000 · 211
10 :43
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The polymorphic allocator is propagated recursively. Child elements of child elements will use the same memory resource as the parent. 134/10000 · 134
10 :26
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Parse a string containing a complete serialized JSON text, and return 69/10000 · 69
10 :27
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_object>>, or <<ref_string>>. 34/10000 · 34
11 :13
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https://drone.io/[Drone] 24/10000 · 24
11 :78
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_has_value_from>> + <<ref_has_value_to>> + <<ref_is_deallocate_trivial>> + <<ref_is_described_class>> + <<ref_is_described_enum>> + <<ref_is_map_like>> + <<ref_is_null_like>> + <<ref_is_optional_like>> + <<ref_is_path_like>> + <<ref_is_sequence_like>> + <<ref_is_string_like>> + <<ref_is_tuple_like>> + <<ref_is_variant_like>> + <<ref_result_for>> + <<ref_try_value_to_tag>> + <<ref_value_from_tag>> + <<ref_value_to_tag>> 427/10000 · 427
11 :120
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When a library type is used as the element type of a PMR container; that is, a container which uses a {ref_polymorphic_allocator}, the memory resource will automatically propagate to the type and all of its children: 216/10000 · 216
:39 :39
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Parses the input using an instance of 37/10000 · 37
11 :63
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — {icon_bad} Poor separation of concerns. The `basic_json` container 66/10000 · 66
11 :54
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Similar to the `std` counterpart, elements may be accessed directly by their key with bounds checking using <<ref_object_at>>, or without bounds checking using <<ref_object_operator_lb_rb>> which creates a null element if the key does not already exist: 253/10000 · 253
11 :100
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In all cases, the <<ref_storage_ptr>> owned by an <<ref_object>>, <<ref_array>>, or <<ref_value>> constructed from an initializer list will be propagated to each element, recursively. 183/10000 · 183
11 :37
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Working With Values 19/10000 · 19