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

57 :134
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — gcc: 4.8, 4.9, 5, 6, 7, 8, 9, 10, 11, 12 40/10000 · 40
57 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 499KB 5/10000 · 5
57 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_get_uint64>> 24/10000 · 24
57 :137
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — :leveloffset: +1 16/10000 · 16
57 :184
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Resource Lifetime 17/10000 · 17
57 :232
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To achieve performance and memory efficiency, the parser uses a temporary storage area to hold intermediate results. This storage is reused when parsing more than one JSON text, reducing the total number of calls to allocate memory and thus improving performance. Upon construction, the memory resource used to perform allocations for this temporary storage area may be specified. Otherwise, the default memory resource is used. In addition to a memory resource, the parser can make use of a caller-owned buffer for temporary storage. This can help avoid dynamic allocations for small inputs. The following example uses a four kilobyte temporary buffer for the parser, and falls back to the default memory resource if needed: 725/10000 · 725
58 :135
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — msvc: 14.0, 14.1, 14.2, 14.3 28/10000 · 28
58 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A JSON with lots of Cyrillic characters. 40/10000 · 40
:95 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_kind,`kind::double_`>> 28/10000 · 28
58 :139
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — include::custom.adoc[] include::nothrow.adoc[] include::alloc.adoc[] include::context.adoc[] include::forward.adoc[] include::direct.adoc[] include::guidelines.adoc[] 166/10000 · 166
58 :185
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — It is important to note that <<ref_storage_ptr>> supports both shared-ownership and reference lifetime models. Construction from a memory resource pointer does not transfer ownership: 183/10000 · 183
58 :248
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Avoiding Dynamic Allocations 28/10000 · 28
59 :137
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Supported JSON Text 19/10000 · 19
59 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<parse_twitter_json,*twitter.json*>> 37/10000 · 37
59 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https://en.cppreference.com/w/cpp/language/types[`double`] 58/10000 · 58
59 :147
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — :leveloffset: -1 16/10000 · 16
59 :194
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When using a memory resource in this fashion, including the case where a storage pointer or container is constructed from a {ref_polymorphic_allocator}, the caller must ensure that the lifetime of the resource is extended until it is no longer referenced by any variables; otherwise, undefined behavior is possible. 315/10000 · 315
59 :249
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Through careful specification of buffers and memory resources, it is possible to eliminate all dynamic allocation completely when parsing JSON, for the case where the entire JSON text is available in a single character buffer, as shown here: 241/10000 · 241
60 :139
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The library expects input text to be encoded using UTF-8, which is a requirement put on all JSON exchanged between systems by the https://datatracker.ietf.org/doc/html/rfc8259#section-8.1[RFC]. Similarly, the text generated by the library is valid UTF-8. 254/10000 · 254
60 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 617KB 5/10000 · 5