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

5 :30
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — For the class `ip_address` from the section <<custom_conversions>> this overload may look like this: 100/10000 · 100
5 :36
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Comment 7/10000 · 7
5 :37
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — If you need to combine incremental parsing with direct parsing, you can resort to <<ref_parser_for>>. `parser_for<T>` is an instantiation of <<ref_basic_parser>> that parses into an object of type `T`, and is what <<ref_parse_into>> uses under the hood. 253/10000 · 253
5 :38
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Forward declarations of contextual conversions are done very similarly: 71/10000 · 71
5 :28
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — ``` void tag_invoke( const value_from_tag&, value& jv, ip_address const& addr ) { jv = array{ b[0], b[1], b[2], b[3] }; } ``` 125/10000 · 125
5 :21
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<default_memory_resource,default resource>>, an implementation-defined instance which always uses the equivalent of global operator new and delete. 148/10000 · 148
5 :34
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Parameterizing the allocator on the element type is clumsy. 59/10000 · 59
5 :25
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — :leveloffset: -1 16/10000 · 16
5 :21
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — an instance of {ref_polymorphic_allocator} in the same argument position. 73/10000 · 73
5 :18
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A SAX push parser implementation which converts a serialized JSON text into 75/10000 · 75
5 :18
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_operator_lt_lt>> 22/10000 · 22
6 :4
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https://vinniefalco.visualstudio.com/json/_build/latest?definitionId=5&branchName=master[image:https://img.shields.io/azure-devops/build/vinniefalco/2571d415-8cc8-4120-a762-c03a8eda0659/8/master[Build 200/10000 · 200
6 :55
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — *Operators* + 13/10000 · 13
6 :76
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — While keys are strings, the mapped type of objects and the element type of arrays is the aforementioned type <<ref_value>> which can hold any JSON element, as seen in the previous assignments. Instead of building the JSON document using a series of function calls, we can build it in one statement using an initializer list: 324/10000 · 324
6 :26
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — which is optimized for parsing without subsequent modification. The <<ref_stream_parser>> object is reused between trials, allowing temporary memory allocated by the implementation to persist and improve performance. 216/10000 · 216
6 :50
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — This library adopts a "kitchen sink" approach. It contains a wealth of features, even those with niche uses. Its weakness is that the many template parameters, while allowing for configurability, inhibit the best possible optimizations. The consequence is that the library performs poorly. The ability to configure every aspect of the value type has the paradoxical effect of making it less suitable as a vocabulary type. 421/10000 · 421
6 :39
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — :leveloffset: -1 16/10000 · 16
6 :26
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — "Why use <<ref_storage_ptr>> over {ref_polymorphic_allocator}?:: {ref_polymorphic_allocator} treats the memory resource as a reference with respect to ownership. Boost.JSON uses a reference counted smart pointer container to simplify the lifetime management of memory resources. In addition to being reference counted, <<ref_storage_ptr>> can function as an uncounted reference wrapper around a {ref_memory_resource}. 417/10000 · 417
6 :26
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — All inserted values will use the same {ref_memory_resource} as the container 76/10000 · 76
6 :52
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To resolve the ambiguity manually, use an explicit constructor: 63/10000 · 63