2. Boost Json Translation (zh_Hans)
3. Doc / Pages / Dom / Init Lists (adoc)
4. English
5. Zen

4 :34
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When a two element initializer list is nested within an enclosing initializer list, it is unclear whether it represents an <<ref_array>> or an <<ref_object>>: 158/10000 · 158
5 :43
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In such cases, if every element consists of a string followed by a single value, then the enclosing initializer list is interpreted as an <<ref_object>>. Otherwise, it is interpreted as an <<ref_array>>. 203/10000 · 203
6 :52
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To resolve the ambiguity manually, use an explicit constructor: 63/10000 · 63
7 :59
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Initializer lists can be used to unambiguously construct or assign an <<ref_object>> or <<ref_array>>: 102/10000 · 102
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
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
10 :87
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Elements that are rvalues will be moved upon initialization: 60/10000 · 60
11 :100
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In all cases, the <<ref_storage_ptr>> owned by an <<ref_object>>, <<ref_array>>, or <<ref_value>> constructed from an initializer list will be propagated to each element, recursively. 183/10000 · 183
The translation has come to an end.