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

15 :91
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Formatted Output 16/10000 · 16
15 :67
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — After a <<ref_value>> is constructed, its kind can change depending on what is assigned to it, or by calling functions such as <<ref_value_emplace_array,`value::emplace_array`>> or <<ref_value_emplace_bool,`value::emplace_bool`>>. If the assignment is successful, in other words it completes without any exceptions then the value is replaced. Otherwise, the value is unchanged. All operations which can fail to modify a value offer the strong exception safety guarantee. 470/10000 · 470
15 :38
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — types. |=== 11/10000 · 11
15 :45
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — a `std::string` parameter and two `size_type` parameters that specify a 71/10000 · 71
15 :99
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Combining Contexts 18/10000 · 18
15 :72
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — While overloads of `tag_invoke` called by <<ref_value_to>> take the form: 73/10000 · 73
15 :58
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `std::int64_t`, if `T` is a signed integer'; or 47/10000 · 47
15 :41
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_get_null_resource>> 25/10000 · 25
15 :91
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — This can be worked around by declaring the container to use a custom allocator (perhaps using a `std::shared_ptr< std::pmr::memory_resource >` as a data member). This hinders library composition; every library now exports unique, incompatible container types. A raw memory resource pointer is also easy to misuse: 313/10000 · 313
15 :38
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_stream_parser>> 21/10000 · 21
15 :42
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The <<ref_serialize>> function converts a <<ref_value>> into a {std_string}: 76/10000 · 76
16 :23
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — http://www.boost.org/development/tests/develop/developer/json.html[image:https://img.shields.io/badge/matrix-develop-brightgreen.svg[Matrix]] 141/10000 · 141
16 :154
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Error codes are also possible: 30/10000 · 30
16 :56
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — *nlohmann* 10/10000 · 10
16 :72
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — {icon_bad} Slow parsing and serialization performance. 54/10000 · 54
16 :93
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When an <<ref_object>> is formatted to a {std_ostream}, the result is a valid JSON. That is, the object will be output with curly braces and a comma separated list of key/value pairs, as per the JSON specification. 214/10000 · 214
16 :80
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The following table shows all of the ways to determine and access the contents of a <<ref_value>>: 98/10000 · 98
16 :41
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — These containers are explored in-depth in the sections that follow. 67/10000 · 67
16 :46
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — substring, or 13/10000 · 13
16 :100
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Often it is needed to use several conversion contexts together. For example, consider a log of remote users identified by IP addresses accessing a system. We can represent it as `std::vector<std::pair<std::chrono::system_clock::time_point, ip_address>>`. We want to serialize both ``ip_address``es and ``time_point``s as strings, but for this we need both `as_string` and `as_iso_8601` contexts. To combine several contexts just use {std_tuple}. Conversion functions will select the first element of the tuple for which a `tag_invoke` overload exists and will call that overload. As usual, `tag_invoke` overloads that don't use contexts and library-provided generic conversions are also supported. Thus, here's our example: 723/10000 · 723