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

44 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_emplace_int64>> 27/10000 · 27
44 :87
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Type satisfying <<ref_is_described_class>> 42/10000 · 42
44 :108
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Consider the pattern of memory allocation during parsing: when an array, object, or string is encountered the parser accumulates elements in its temporary storage area. When all of the elements are known, a single memory allocation is requested from the resource when constructing the value. Thus, parsing only allocates and constructs containers at their final size. Memory is not reallocated; that is, a memory buffer never needs to grow by allocating a new larger buffer and deallocating the previous buffer. 511/10000 · 511
44 :181
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Streaming Parser 16/10000 · 16
45 :94
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The library relies heavily on these well known C++ types in its interfaces (henceforth termed _standard types_): 112/10000 · 112
45 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 2.91MB 6/10000 · 6
45 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_is_int64>> 22/10000 · 22
45 :87
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The result is an <<ref_object>> with described members' names as keys. 70/10000 · 70
45 :116
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The <<ref_monotonic_resource>> optimizes this memory allocation pattern by allocating increasingly large blocks of global memory internally and parceling those blocks out in smaller pieces to fulfill allocation requests. It has a trivial deallocate function. The monotonic resource does not actually deallocate memory until the resource is destroyed. Thus, it is ideally suited for the use-case where JSON is parsed, and the resulting value is then inspected but not modified. 476/10000 · 476
45 :182
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The <<ref_stream_parser>> implements a https://en.wikipedia.org/wiki/Online_algorithm[__streaming algorithm__]; it allows incremental processing of large JSON inputs using one or more contiguous character buffers. The entire input JSON does not need to be loaded into memory at once. A network server can use the streaming interface to process incoming JSON in fixed-size amounts, providing these benefits: 406/10000 · 406
46 :97
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `string_view` 13/10000 · 13
46 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A three.js example model serialized to JSON. 44/10000 · 44
46 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_if_int64>> 22/10000 · 22
46 :87
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The result is default-constructed and described members are assigned 68/10000 · 68
46 :124
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The resource to use when constructing values may be specified in calls to <<ref_parse>> as shown here: 102/10000 · 102
46 :189
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — CPU consumption per I/O cycle is bounded 40/10000 · 40
47 :98
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `memory_resource`, `polymorphic_allocator` 42/10000 · 42
47 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<parse_mesh_json,*mesh.json*>> 31/10000 · 31
47 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_try_as_int64>> 26/10000 · 26
47 :106
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — corresponding values. 21/10000 · 21