2. Boost Json Translation (zh_Hans)
3. Doc / Pages / Conversion / Context (adoc)
4. English
5. Zen

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
8 :63
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Reverse conversion is left out for brevity. 43/10000 · 43
9 :65
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The new context is used in a similar fashion to `as_string` previously in this section. 87/10000 · 87
10 :73
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — One particular use case that is enabled by contexts is adaptor libraries that define JSON conversion logic for types from a different library. 142/10000 · 142
11 :76
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Passing Data to Conversion Functions 36/10000 · 36
12 :77
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Contexts we used so far were empty classes. But contexts may have data members and member functions just as any class. Implementers of conversion functions can take advantage of that to have conversions configurable at runtime or pass special objects to conversions (e.g. allocators). 284/10000 · 284
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
14 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — This `tag_invoke` overload lets us change date conversion format at runtime. Also note, that there is no ambiguity between `as_iso_8601` overload and `date_format` overload. You can use both in your program: 207/10000 · 207
15 :99
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Combining Contexts 18/10000 · 18
16 :100
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Often it is needed to use several conversion contexts together. For example, consider a log of remote users identified by IP addresses accessing a system. We can represent it as `std::vector<std::pair<std::chrono::system_clock::time_point, ip_address>>`. We want to serialize both ``ip_address``es and ``time_point``s as strings, but for this we need both `as_string` and `as_iso_8601` contexts. To combine several contexts just use {std_tuple}. Conversion functions will select the first element of the tuple for which a `tag_invoke` overload exists and will call that overload. As usual, `tag_invoke` overloads that don't use contexts and library-provided generic conversions are also supported. Thus, here's our example: 723/10000 · 723
17 :117
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In this snippet `time_point` is converted using `tag_invoke` overload that takes `as_iso_8601`, `ip_address` is converted using `tag_invoke` overload that takes `as_string`, and {std_vector} is converted using a generic conversion provided by the library. 255/10000 · 255
18 :122
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Contexts and Composite Types 28/10000 · 28
19 :123
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — As was shown previously, generic conversions provided by the library forward contexts to conversions of nested objects. And in the case when you want to provide your own conversion function for a composite type enabled by a particular context, you usually also need to do that. 277/10000 · 277
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
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
The translation has come to an end.