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

13 :19
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Status]] |https://drone.cpp.al/boostorg/json[image:https://drone.cpp.al/api/badges/boostorg/json/status.svg?ref=refs/heads/develop[Build Status]] 145/10000 · 145
13 :141
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A counted memory resource will not be destroyed until every container with shared ownership of the resource is destroyed. 121/10000 · 121
13 :47
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — *rapidjson* 11/10000 · 11
13 :66
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — {icon_bad} Limited allocator support. Only stateless allocators are allowed, 76/10000 · 76
13 :83
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — For the complete listing of all available member functions and nested types, see the reference page for <<ref_object>>. 119/10000 · 119
13 :46
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The member function <<ref_value_kind,`value::kind`>> may be used to query the kind stored in the value. Alternatively, member functions like <<ref_value_is_object,`value::is_object`>> <<ref_value_is_number,`value::is_number`>> may be used to check whether or not the value is a particular kind: 294/10000 · 294
13 :36
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value>> 13/10000 · 13
13 :41
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — More formally, `std::string` member function overloads that accept any of the following parameter combinations as an input string: 130/10000 · 130
13 :82
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Let's rewrite conversion for ``system_clock::time_point``s to allow any format supported by `std::strftime`. 108/10000 · 108
13 :66
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Overloads of `tag_invoke` called by <<ref_value_from>> take the form: 69/10000 · 69
13 :36
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https://en.cppreference.com/w/cpp/types/is_arithmetic[Arithmetic type] 70/10000 · 70
13 :41
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Name 4/10000 · 4
13 :70
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The memory resource is passed by pointer; ownership is not transferred. The caller is responsible for extending the lifetime of the memory resource until the last container which is using it goes out of scope, otherwise the behavior is undefined. Sometimes this is the correct model, such as in this example which uses a monotonic resource constructed from a local stack buffer: 378/10000 · 378
:33 :33
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A stateful DOM parser object which may be used to efficiently parse a series 76/10000 · 76
13 :31
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — instances of <<ref_value>>, <<ref_array>>, <<ref_object>>, or <<ref_string>>. |=== 82/10000 · 82
14 :23
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Matrix 6/10000 · 6
14 :145
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Parsing 7/10000 · 7
:47 :47
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Parses the input using an instance of 37/10000 · 37
14 :67
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — which rules out the most important type of allocator, a local arena-based implementation. 89/10000 · 89
14 :86
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — As with `std::pair`, the <<ref_key_value_pair>> type can be used with structured bindings in {cpp}17. Specializations of `std::tuple_size`, `std::tuple_element`, and overloads of <<ref_get>> are all provided for this purpose. 225/10000 · 225