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

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
16 :74
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — ``` T tag_invoke( const value_to_tag< T >&, const value& ); ``` 63/10000 · 63
16 :59
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `std::uint64_t`, if `T` is an unsigned integer; or 50/10000 · 50
16 :41
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Returns a pointer to a memory resource instance which always throws an 70/10000 · 70
16 :102
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Workarounds for this problem are worse than the problem itself. The library could return a pair with the vector and `std::unique_ptr<std::pmr::memory_resource>` which the caller must manage. Or the library could change its function signatures to accept a {ref_memory_resource}``*`` provided by the caller, where the library also makes public the desired memory resources (`my_resource` above). 393/10000 · 393
:38 :38
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A stateful DOM parser object which may be used to efficiently parse a series 76/10000 · 76
16 :49
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In situations where serializing a <<ref_value>> in its entirety is inefficient or even impossible, <<ref_serializer>> can be used to serialize a <<ref_value>> incrementally. This may be done for a variety of reasons, such as to avoid buffering the entire output, or to ensure that a fixed amount of work is performed in each cycle. Instances of <<ref_serializer>> maintain an output state using internal dynamically allocated structures, with an interface to retrieve successive buffers of the serialized output into a caller provided buffer. Here is an example, demonstrating how <<ref_operator_lt_lt>> may be implemented using a <<ref_serializer>>: 650/10000 · 650
17 :23
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Fuzzing 7/10000 · 7
17 :161
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — By default, the parser is strict and only accepts JSON compliant with the standard. However this behavior can be relaxed by filling out an options structure enabling one or more extensions. Here we use a static buffer and enable two non-standard extensions: 257/10000 · 257
17 :56
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Parses the input using the static member function 49/10000 · 49
17 :74
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — {icon_good} Full-featured, including JSON Pointer, CBOR, and others. 68/10000 · 68
17 :83
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — .<<ref_value>> Accessors [%autowidth,cols=8] |=== |Kind |Representation |Emplacement |Kind Test |Pointer Access |`result` Access |Checked Access |Unchecked Access 162/10000 · 162
17 :55
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — :leveloffset: +1 include::value.adoc[] include::string.adoc[] include::array.adoc[] include::object.adoc[] include::numbers.adoc[] include::init_lists.adoc[] include::nested_access.adoc[] :leveloffset: -1 204/10000 · 204
17 :47
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — a parameter of a type convertible to <<ref_string_view>>, or 60/10000 · 60