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

28 :243
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To go from JSON to a user-defined type we use <<ref_value_to>>, which uses another overload of `tag_invoke`. This converts a JSON value to a `customer`. It throws an exception if the contents of the value do not match what is expected: 235/10000 · 235
28 :78
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<parse_canada_json,*canada.json*>> 35/10000 · 35
:106 :106
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — {icon_bad} No incremental parsing, no incremental serialization. 64/10000 · 64
28 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_emplace_object>> 28/10000 · 28
28 :88
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When a <<ref_string>> is formatted to a {std_ostream}, the result is a valid JSON. That is, the result will be double quoted and the contents properly escaped per the JSON specification. 186/10000 · 186
28 :61
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `std::variant` and similar types, e.g. `boost::variant2::variant`. 66/10000 · 66
28 :62
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — deallocate function. Allocated memory is not freed until the resource is destroyed, making it fast for parsing but not suited for performing modifications. 155/10000 · 155
28 :103
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When `allow_invalid_utf16` is enabled, the parser will not throw an error in the case of illegal leading, trailing, or half a surrogate. Instead, it will replace the invalid UTF-16 code point(s) with the Unicode replacement character. 234/10000 · 234
29 :58
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — This library focuses on a common and popular use-case: parsing and serializing to and from a container called `value` which holds JSON types. Any `value` which you build can be serialized and then deserialized, guaranteeing that the result will be equal to the original value. Whatever JSON output you produce with this library will be readable by most common JSON implementations in any language. 397/10000 · 397
29 :253
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The code above defines the convenience function `extract`, which deduces the types of the struct members. This works, but requires that the struct is {req_DefaultConstructible}. An alternative is to construct the object directly, which is a little more verbose but doesn't require default construction: 302/10000 · 302
29 :78
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 2.2MB 5/10000 · 5
29 :108
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — {icon_good} Parsing and serialization performance is better than most other 75/10000 · 75
29 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_is_object>> 23/10000 · 23
29 :92
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Accessing Storage Beyond `size()` 33/10000 · 33
29 :61
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The result is equal to the result of conversion of the active variant 69/10000 · 69
29 :66
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — {ref_polymorphic_allocator} 27/10000 · 27
29 :113
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When enabling comment support take extra care not to drop whitespace 68/10000 · 68
30 :65
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The `value` container is designed to be well suited as a vocabulary type appropriate for use in public interfaces and libraries, allowing them to be composed. The library restricts the representable data types to the ranges which are almost universally accepted by most JSON implementations, especially JavaScript. The parser and serializer are both highly performant, meeting or exceeding the benchmark performance of the best comparable libraries. Allocators are very well supported. Code which uses these types will be easy to understand, flexible, and performant. 567/10000 · 567
30 :263
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Now we can construct customers from JSON: 41/10000 · 41
30 :78
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The largest file, containing a large number of 2-element arrays holding 71/10000 · 71