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

19 :114
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `T` is not a class template 27/10000 · 27
19 :42
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A low level building block used for efficiently building a <<ref_value>>. The 77/10000 · 77
20 :23
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https://ci.appveyor.com/[Appveyor] 34/10000 · 34
20 :190
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Serializing 11/10000 · 11
20 :66
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The input files are all loaded first. Then each configuration is run for a sufficient number of trials to last at least 5 seconds. The elapsed time, number of invocations (of parse or serialize), and bytes transferred are emitted as a sample along with a calculation of throughput expressed in megabytes per second. Several samples (currently five) are generated for each configuration. All but the median two samples are discarded, with the remaining samples averaged to produce a single number which is reported as the benchmark result. 538/10000 · 538
20 :93
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — {icon_bad} The value type is not regular. Assignment is destructive, 68/10000 · 68
20 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_emplace_array>> 27/10000 · 27
20 :50
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — a `const_pointer` parameter, or 31/10000 · 31
20 :128
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Consider this example. As was discussed in a previous section, <<ref_is_map_like>> requires that your key type satisfies <<ref_is_string_like>>. Now, let's say your keys are not string-like, but they do convert to <<ref_string>>. You can make such maps to also convert to objects using a context. But if you want to also use another context for values, you need a way to pass the full combined context to map elements. So, you want the following test to succeed. 462/10000 · 462
20 :61
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Intended for types like {std_monostate}. 40/10000 · 40
20 :51
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — to deallocate are trivial. 26/10000 · 26
20 :115
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `T` references a {ref_memory_resource} 38/10000 · 38
20 :44
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — parsers use this internally, and users may use it to adapt foreign parsers to produce this library's containers. |=== 117/10000 · 117
21 :23
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https://ci.appveyor.com/project/vinniefalco/cppalliance-json/branch/master[image:https://ci.appveyor.com/api/projects/status/8csswcnmfm798203?branch=master&svg=true[Build 170/10000 · 170
21 :191
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Simple free functions are provided for serializing a <<ref_value>> to a {std_string} containing JSON: 101/10000 · 101
21 :75
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The input files, available in the bench/data directory, are laid out thusly: 76/10000 · 76
21 :94
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — performing `a = b` is equivalent to `a = std::move(b)`. No copy construction or copy assignment allowed. 104/10000 · 104
21 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_is_array>> 22/10000 · 22
21 :51
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — a parameter of type `const_pointer` and a `size_type` parameter that 68/10000 · 68
21 :141
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — For this you will have to use a different overload of `tag_invoke`. This time it has to be a function template, and it should have two parameters for contexts. The first parameter is the specific context that disambiguates that particular overload. The second parameter is the full context passed to <<ref_value_to>> or <<ref_value_from>>. 339/10000 · 339