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

5 :18
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A sequence container of JSON values supporting dynamic size and fast, random 76/10000 · 76
5 :22
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_string>> uses `char` as its character type, 49/10000 · 49
5 :55
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In settings where exceptions cannot be used, an overload of `value::to_number` accepting {ref_error_code} can be used instead with identical semantics to its throwing counterpart: 179/10000 · 179
5 :30
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — If your users are external, they and not you decide whether throwing exceptions is acceptable. So, in this case it is better to use non-throwing `tag_invoke` overloads. In addition, for customising conversion of composite types, always use `tag_invoke` overload with 2 context parameters. This will allow correct context propagation to elements of composites. This will also allow propagation of exceptions from conversion of elements. 435/10000 · 435
5 :46
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Conversions for Third-Party Types 33/10000 · 33
5 :32
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — It exposes both a sequence API and a tuple API. But converting from <<ref_value>> to `user_ns::ip_address` would not be able to use implementation for sequences, since those are constructed empty and then populated one element at a time, while `ip_address` has a fixed size of 4. The tuple conversion would fit, though. The only problem is that <<ref_is_tuple_like>> has a lower priority than <<ref_is_sequence_like>>. In order to circumvent this, the user only needs to specialize <<ref_is_sequence_like>> to not match `ip_address`. 533/10000 · 533
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