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

42 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 216KB 5/10000 · 5
:95 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_kind,`kind::int64`>> 26/10000 · 26
42 :87
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A heterogenous sequence with fixed size, e.g. `std::tuple` and `std::pair`. 75/10000 · 75
42 :103
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — This memory resource is not guaranteed to be the same as the result of `boost::container::pmr::get_default_resource`. It also cannot be changed with `boost::container::pmr::set_default_resource`. 195/10000 · 195
42 :162
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Sometimes a protocol may have a JSON text followed by data that is in a different format or specification. The JSON portion can still be parsed by using the function <<ref_parser_write_some>>. Upon success, the return value will indicate the number of characters consumed from the input, which will exclude the non-JSON characters: 331/10000 · 331
43 :91
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — (see below) 11/10000 · 11
43 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — An array of large objects. 26/10000 · 26
43 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https://en.cppreference.com/w/cpp/types/integer[`std::int64_t`] 63/10000 · 63
43 :87
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The result is constructed with the array elements as constructor arguments. 75/10000 · 75
43 :107
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Monotonic Resource 18/10000 · 18
43 :173
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The parser instance may be constructed with parse options which allow some non-standard JSON extensions to be recognized: 121/10000 · 121
44 :92
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Supports -fno-exceptions, detected automatically 48/10000 · 48
44 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<parse_marine_ik_json,*marine_ik.json*>> 41/10000 · 41
44 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_emplace_int64>> 27/10000 · 27
44 :87
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Type satisfying <<ref_is_described_class>> 42/10000 · 42
44 :108
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Consider the pattern of memory allocation during parsing: when an array, object, or string is encountered the parser accumulates elements in its temporary storage area. When all of the elements are known, a single memory allocation is requested from the resource when constructing the value. Thus, parsing only allocates and constructs containers at their final size. Memory is not reallocated; that is, a memory buffer never needs to grow by allocating a new larger buffer and deallocating the previous buffer. 511/10000 · 511
44 :181
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Streaming Parser 16/10000 · 16
45 :94
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The library relies heavily on these well known C++ types in its interfaces (henceforth termed _standard types_): 112/10000 · 112
45 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 2.91MB 6/10000 · 6
45 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_is_int64>> 22/10000 · 22