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

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
9 :60
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — {icon_bad} Too much customization. We struggle to see a use case for making 75/10000 · 75
9 :38
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Initializer lists consisting of two-element key value pairs can be used to construct objects with initial contents. These constructors may allocate memory and throw: 165/10000 · 165
9 :77
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The requirement for an initializer list to be interpreted as an <<ref_object>> or <<ref_array>> when initializing such an entity only applies to the outermost initializer list; subsequent nested elements will follow the usual ambiguity resolution rules. 253/10000 · 253
9 :34
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — **object**: A collection of name/value pairs, also known as an 62/10000 · 62
9 :28
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — is a string and the mapped type is a JSON value. Search, insertion, and removal have average contant-time complexity. In addition, elements are stored contiguously in memory allowing cache-friendly iteration. 208/10000 · 208
9 :26
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_storage_ptr>> is used instead of {req_Allocator}, and 59/10000 · 59
9 :79
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — contains an exponent, or 24/10000 · 24
9 :65
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The new context is used in a similar fashion to `as_string` previously in this section. 87/10000 · 87
9 :56
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — customization point, and 24/10000 · 24
:36 :36
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Custom behavior. 16/10000 · 16
9 :30
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — ownership of the memory resource; the lifetime of the resource is extended until all copies of the storage pointer are destroyed. 129/10000 · 129
9 :42
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Polymorphic Allocators 22/10000 · 22