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

4 :27
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Direct parsing is performed by the <<ref_parse_into>> family of functions. The library provides overloads that take either <<ref_string_view>> or `std::istream`, and can report errors either via throwing exceptions or setting an error code. 240/10000 · 240
4 :33
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — As discussed previously, we prefer to define a non-throwing overload of `tag_invoke` for <<ref_try_value_to>>, rather then the throwing overload for <<ref_value_to>>, as the latter can fallback to the former without performance degradation. 240/10000 · 240
4 :25
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — For example, consider this alternative implementation of `tag_invoke` for `ip_address` from the section <<custom_conversions>>. 127/10000 · 127
4 :20
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Default-constructed storage pointers reference the 50/10000 · 50
4 :33
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The container must be a class template. 39/10000 · 39
4 :21
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — include::background.adoc[] include::storage_ptr.adoc[] include::uses_allocator.adoc[] 85/10000 · 85
4 :20
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — All eligible constructors which accept <<ref_storage_ptr>> will also accept 75/10000 · 75
4 :18
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_basic_parser>> 20/10000 · 20
4 :18
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Description 11/10000 · 11
4 :22
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — :leveloffset: -1 16/10000 · 16
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