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

6 :26
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — which is optimized for parsing without subsequent modification. The <<ref_stream_parser>> object is reused between trials, allowing temporary memory allocated by the implementation to persist and improve performance. 216/10000 · 216
6 :50
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — This library adopts a "kitchen sink" approach. It contains a wealth of features, even those with niche uses. Its weakness is that the many template parameters, while allowing for configurability, inhibit the best possible optimizations. The consequence is that the library performs poorly. The ability to configure every aspect of the value type has the paradoxical effect of making it less suitable as a vocabulary type. 421/10000 · 421
6 :39
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — :leveloffset: -1 16/10000 · 16
6 :26
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — "Why use <<ref_storage_ptr>> over {ref_polymorphic_allocator}?:: {ref_polymorphic_allocator} treats the memory resource as a reference with respect to ownership. Boost.JSON uses a reference counted smart pointer container to simplify the lifetime management of memory resources. In addition to being reference counted, <<ref_storage_ptr>> can function as an uncounted reference wrapper around a {ref_memory_resource}. 417/10000 · 417
6 :26
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — All inserted values will use the same {ref_memory_resource} as the container 76/10000 · 76
6 :52
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To resolve the ambiguity manually, use an explicit constructor: 63/10000 · 63
6 :29
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — **string**: A sequence of zero or more Unicode characters, 58/10000 · 58
6 :52
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — For the complete listing of all available member functions and nested types, see the reference page for <<ref_array>>. 118/10000 · 118
6 :23
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — access. The interface and performance characteristics are similar to {std_vector}. 82/10000 · 82
6 :23
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — redundant overloads for string operations have been replaced 60/10000 · 60
6 :64
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When parsing a JSON document, the type used to represent a number is not explicitly specified and must be determined from its value. In general, the parser will choose the best type which can accurately store the number as it appears in the document. Integers (i.e. numbers without decimals or exponents) that cannot be represented by `std::uint64_t` and `std::int64_t` will be represented as `double` to preserve their magnitude: 430/10000 · 430
6 :37
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Finally, it is worth mentioning that due to the ability to provide conversions to JSON containers without a binary dependency on the library, you don't have to push such dependency on your users. This is particularly relevant for libraries for which interoperation with Boost.JSON is only ancillary. 299/10000 · 299
6 :47
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Normally, you wouldn't be able to provide conversions for types from third-party libraries and standard types, because it would require yout to put `tag_invoke` overloads into namespaces you do not control. But with contexts you can put the overloads into your namespaces. This is because the context will add its associated namespaces into the list of namespaces where `tag_invoke` overloads are searched. 406/10000 · 406
6 :45
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `tag_invoke` Overloads 22/10000 · 22
6 :38
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The overload lets us use `ip_address` with <<ref_try_value_to>>. 64/10000 · 64
6 :36
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `value_from` behavior 21/10000 · 21
6 :42
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Direct serialization doesn't require any special components and works with the regular <<ref_serializer>> and <<ref_serialize>>. 128/10000 · 128
6 :36
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — This implementation explicitly creates an <<ref_array>> rather than relying on assignment from an initializer list. But the array uses default {ref_memory_resource}, not the one used by `jv`. 191/10000 · 191
6 :24
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Storage pointers constructed from a {ref_memory_resource} or 60/10000 · 60
6 :35
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The system of allocator traits, especially POCCA and POCMA, 59/10000 · 59