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

48 :139
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A monotonic resource may be optionally constructed with an initial buffer to use first, before going to the heap. This allows the caller to use stack space and avoid dynamic allocations for most parsed JSON, falling back to dynamic allocation from the heap if the input JSON is larger than average, as shown here: 313/10000 · 313
48 :191
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Jitter, unfairness, and latency is reduced 42/10000 · 42
49 :101
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Header-Only 11/10000 · 11
49 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A JSON representing a 3D mesh. Contains many floating-point numbers. 68/10000 · 68
49 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_get_int64>> 23/10000 · 23
49 :108
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — If the input value is equal to one of the described enumerators, the result is 78/10000 · 78
49 :150
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Static Resource 15/10000 · 15
49 :192
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Less total memory is required to process the full input 55/10000 · 55
50 :103
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To use as header-only; that is, to eliminate the requirement to link a program to a static or dynamic Boost.JSON library, simply place the following line in exactly one new or existing source file in your project. 213/10000 · 213
50 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<parse_mesh_pretty_json,*mesh.pretty.json*>> 45/10000 · 45
:95 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_kind,`kind::uint64`>> 27/10000 · 27
50 :111
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — a <<ref_string>>, containing its name. Otherwise it's equal to the input value converted to its underlying type. |The result is the described enumerator, corresponding to the input <<ref_string>>. 196/10000 · 196
50 :151
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A <<ref_static_resource>> constructs from a caller-provided buffer, and satisfies all memory allocation requests from the buffer. Once the buffer is exhausted, subsequent calls to allocate throw the exception `std::bad_alloc`. The resource offers a simple invariant: dynamic heap allocations are never performed. 312/10000 · 312
50 :194
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To use the <<ref_stream_parser>>, declare an instance. Then call <<ref_stream_parser_write>> zero or more times with successive buffers representing the input JSON. When there are no more buffers, call <<ref_stream_parser_finish>>. The function <<ref_stream_parser_done>> returns `true` after a successful call to `write` or `finish` if parsing is complete. 357/10000 · 357
51 :112
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — MSVC users must also define the macro `BOOST_JSON_NO_LIB` to disable auto-linking. 82/10000 · 82
51 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 1.54MB 6/10000 · 6
51 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https://en.cppreference.com/w/cpp/types/integer[`std::uint64_t`] 64/10000 · 64
51 :116
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Type satisfying <<ref_is_path_like>>. 37/10000 · 37
51 :157
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To use the resource, construct it with a local buffer: 54/10000 · 54
51 :200
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In the following example a JSON text is parsed from standard input a line at a time. Error codes are used instead. The function <<ref_stream_parser_finish>> is used to indicate the end of the input: 198/10000 · 198