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

6 :18
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Serialize a <<ref_value>>, <<ref_array>>, <<ref_object>>, or <<ref_string>> 75/10000 · 75
7 :9
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Status]] |https://vinniefalco.visualstudio.com/json/_build/latest?definitionId=8&branchName=develop[image:https://img.shields.io/azure-devops/build/vinniefalco/2571d415-8cc8-4120-a762-c03a8eda0659/8/develop[Build Status]] 221/10000 · 221
7 :56
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_operator_eq_eq>> + <<ref_operator_not_eq>> + <<ref_operator_gt>> + <<ref_operator_gt_eq>> + <<ref_operator_lt>> + <<ref_operator_lt_eq>> + <<ref_operator_lt_lt>> + 169/10000 · 169
7 :87
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When a <<ref_value>>, <<ref_array>>, or <<ref_object>> is assigned or constructed from an initializer list, the creation of the new value happens only once. This makes initializer lists equally efficient as using the other ways to create a value. The types in this library are first-class, supporting copy and move construction and assignment: 343/10000 · 343
7 :32
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — *boost* 7/10000 · 7
7 :57
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — {icon_bad} `basic_json` is a class template. Libraries must agree on the 72/10000 · 72
7 :34
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The string provided by the 26/10000 · 26
7 :27
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — itself. 7/10000 · 7
7 :59
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Initializer lists can be used to unambiguously construct or assign an <<ref_object>> or <<ref_array>>: 102/10000 · 102
7 :30
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — similar to {std_string}. 24/10000 · 24
7 :55
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Formatted Output 16/10000 · 16
7 :26
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_object>> 14/10000 · 14
7 :24
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — with a <<ref_string_view>>-based interface, 43/10000 · 43
7 :76
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — More formally, if the number: 29/10000 · 29
7 :54
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — As an example, let's implement conversion for https://en.cppreference.com/w/cpp/chrono/system_clock[``std::chrono::system_clock::time_point``s] using https://en.wikipedia.org/wiki/ISO_8601[ISO 8601] format. 206/10000 · 206
7 :46
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The second, more powerful approach, is to provide the conversion implementation yourself. With Boost.JSON this is done by defining an overload of `tag_invoke` function (the benefits of this mechanism are outlined in http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1895r0.pdf[C++ proposal P1895]. In essence, `tag_invoke` provides a uniform interface for defining customization points by using argument-dependent lookup to find a viable overload from the point at which it is called. As the name suggests, a tag type is passed as an argument in order to: 562/10000 · 562
7 :45
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — If <<ref_try_value_to>> is used with a type, for which there's no `tag_invoke` overload of the form described in this section, but there is one of the form intended for <<ref_value_to>>, then the library still tries to perform the conversion. It uses the throwing overload, and attempts to convert any thrown exception into an {ref_error_code}. Note, though, that such approach will likely be slower then a dedicated overload. 426/10000 · 426
7 :36
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `value_to` behavior 19/10000 · 19
7 :40
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To avoid creating such temporaries with an incorrect {ref_memory_resource}, using <<ref_value>>'s member functions <<ref_value_emplace_array>>, <<ref_value_emplace_object>>, and <<ref_value_emplace_string>> can be helpful. 222/10000 · 222
7 :25
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — {ref_polymorphic_allocator} do not acquire ownership; the caller is responsible for ensuring that the lifetime of the resource extends until it is no longer referenced. 168/10000 · 168