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

8 :29
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — An empty object may be constructed without incurring any memory allocations using the <<default_memory_resource,default memory resource>>. A <<ref_storage_ptr>> can also be explicitly specified: 194/10000 · 194
8 :67
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Similarly, an initializer list for an <<ref_object>> is always interpreted as an <<ref_object>>. In such cases, the initializer list must be a list of key-value pairs. For example, the following code will not compile because `1` is not convertible to a string: 260/10000 · 260
8 :32
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — **array**: An ordered list of values, like {std_vector}. 56/10000 · 56
8 :57
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When an <<ref_array>> is formatted to a {std_ostream}, the result is a valid JSON. That is, the array will be output with square brackets and the comma separated list of values, as per the JSON specification. 208/10000 · 208
8 :26
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — An associative container of key-value pairs with unique keys, where the key 75/10000 · 75
8 :25
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — access to characters in the range `[size(), capacity())` is permitted, 70/10000 · 70
8 :78
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — contains a decimal point, or 28/10000 · 28
8 :63
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Reverse conversion is left out for brevity. 43/10000 · 43
8 :55
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — discard candidates that are unrelated to that particular 56/10000 · 56
8 :52
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The opposite is also true: if there's a `tag_invoke` overload intended for <<ref_try_value_to>>, but not for <<ref_value_to>>, then calling <<ref_value_to>> will invoke the non-throwing overload, then construct a {ref_system_error} from the {ref_error_code} and throw it. Due to these fallbacks, it is recommended that users provide the overload from this section, rather then the other one, if they ever intend to use <<ref_try_value_to>>. 440/10000 · 440
8 :36
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Custom conversion. 18/10000 · 18
8 :29
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A storage pointer obtained from <<ref_make_shared_resource>> acquires shared 76/10000 · 76
8 :38
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Allocator-based programs which use multiple allocator types incur a greater number of function template instantiations and are generally slower to compile because class template function definitions must be visible at all call sites. 233/10000 · 233
8 :27
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Practically, this means that when a library container type is used in a standard container that uses a polymorphic allocator, the allocator will propagate to the JSON type. For example: 185/10000 · 185
8 :26
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A structure used to select which extensions are enabled during parsing. 71/10000 · 71
8 :25
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_serialize>> 17/10000 · 17
9 :13
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https://www.boost.org/doc/libs/master/libs/json/[image:https://img.shields.io/badge/docs-master-brightgreen.svg[Documentation]] 127/10000 · 127
9 :68
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — *Constants* + <<ref_array_kind>> + <<ref_condition>> + <<ref_error>> + <<ref_kind>> + <<ref_number_precision>> + <<ref_object_kind>> + <<ref_string_kind>> 154/10000 · 154
9 :100
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To permit custom memory allocation strategies, these containers all allow construction with a <<ref_storage_ptr>> which is a smart pointer to a {ref_memory_resource}. The constructor signatures have the same ordering as their `std` equivalents which use {req_Allocator} parameters. Once a container is constructed its memory resource can never change. Here we create an array without performing any dynamic allocations: 419/10000 · 419
9 :34
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — resource>>, which uses the standard C++ allocator, and is designed for general use including mutation of the document after it is parsed. The <<ref_stream_parser>> object is reused between trials, allowing temporary memory allocated by the implementation to persist and improve performance. 290/10000 · 290