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

5 :4
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https://azure.microsoft.com/en-us/services/devops/pipelines/[Azure] 67/10000 · 67
5 :50
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — *P0308R0* + <<ref_pilfer>> + <<ref_pilfered>> + <<ref_is_pilfer_constructible>> 79/10000 · 79
5 :66
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In this library the types <<ref_array>>, <<ref_object>>, and <<ref_string>> hold JSON arrays, objects, and strings respectively while the type <<ref_value>> is a special variant which can hold any JSON element. Here we construct an empty object and then insert the elements above: 280/10000 · 280
5 :36
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — CBOR 4/10000 · 4
5 :21
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Parses the input using a <<ref_monotonic_resource>>, 52/10000 · 52
5 :25
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Value Type: https://github.com/nlohmann/json/blob/00cb98a3d170161711ab912ae6acefba31f29f75/include/nlohmann/json.hpp#L165[`nlohmann::basic_json`] 145/10000 · 145
5 :27
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — include::quick_look.adoc[] include::dom/overview.adoc[] include::allocators/overview.adoc[] include::io/overview.adoc[] include::conversion/overview.adoc[] include::examples.adoc[] include::faq.adoc[] include::benchmarks.adoc[] include::comparison.adoc[] include::reference.adoc[] include::../../CHANGELOG.adoc[] 312/10000 · 312
5 :21
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — require that <<ref_value>> be declared as a class template, which would impose an additional compilation burden. By avoiding the template, most of the function definitions in the library can be excluded from the headers and emitted in a separate static or dynamic library. 272/10000 · 272
5 :24
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The order of insertions is preserved, as long as there are no removals. 71/10000 · 71
5 :43
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In such cases, if every element consists of a string followed by a single value, then the enclosing initializer list is interpreted as an <<ref_object>>. Otherwise, it is interpreted as an <<ref_array>>. 203/10000 · 203
5 :46
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The specific behavior is controlled by an optional parameter of type <<ref_set_pointer_options>>. For example, here's the same example with a different option: 159/10000 · 159
5 :27
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — **number**: An integral or floating point value. 48/10000 · 48
5 :43
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Similar to its standard library counterpart, elements may be accessed directly by their 0-based index with bounds checking using <<ref_array_at>>, or without bounds checking using <<ref_array_operator_lb_rb>>: 209/10000 · 209
5 :18
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A sequence container of JSON values supporting dynamic size and fast, random 76/10000 · 76
5 :22
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_string>> uses `char` as its character type, 49/10000 · 49
5 :55
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In settings where exceptions cannot be used, an overload of `value::to_number` accepting {ref_error_code} can be used instead with identical semantics to its throwing counterpart: 179/10000 · 179
5 :30
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — If your users are external, they and not you decide whether throwing exceptions is acceptable. So, in this case it is better to use non-throwing `tag_invoke` overloads. In addition, for customising conversion of composite types, always use `tag_invoke` overload with 2 context parameters. This will allow correct context propagation to elements of composites. This will also allow propagation of exceptions from conversion of elements. 435/10000 · 435
5 :46
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Conversions for Third-Party Types 33/10000 · 33
5 :32
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — It exposes both a sequence API and a tuple API. But converting from <<ref_value>> to `user_ns::ip_address` would not be able to use implementation for sequences, since those are constructed empty and then populated one element at a time, while `ip_address` has a fixed size of 4. The tuple conversion would fit, though. The only problem is that <<ref_is_tuple_like>> has a lower priority than <<ref_is_sequence_like>>. In order to circumvent this, the user only needs to specialize <<ref_is_sequence_like>> to not match `ip_address`. 533/10000 · 533
5 :30
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — For the class `ip_address` from the section <<custom_conversions>> this overload may look like this: 100/10000 · 100