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

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
6 :23
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The member function `get_allocator` returns an instance of 58/10000 · 58
6 :23
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — a series of member function calls to a user provided handler. This allows custom behaviors to be implemented for representing the document in memory. 149/10000 · 149
6 :18
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Serialize a <<ref_value>>, <<ref_array>>, <<ref_object>>, or <<ref_string>> 75/10000 · 75
7 :9
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Status]] |https://vinniefalco.visualstudio.com/json/_build/latest?definitionId=8&branchName=develop[image:https://img.shields.io/azure-devops/build/vinniefalco/2571d415-8cc8-4120-a762-c03a8eda0659/8/develop[Build Status]] 221/10000 · 221
7 :56
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_operator_eq_eq>> + <<ref_operator_not_eq>> + <<ref_operator_gt>> + <<ref_operator_gt_eq>> + <<ref_operator_lt>> + <<ref_operator_lt_eq>> + <<ref_operator_lt_lt>> + 169/10000 · 169