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

1 :10
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — = Contextual Conversions Previously in this section we've been assuming that there is a particular fitting JSON representation for a type. But this is not always the case. Often one needs to represent particular value with JSON of certain format in one situation and with another format in a different situation. This can be achieved with Boost.JSON by providing an extra argument---context. 391/10000 · 391
2 :17
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Let's implement conversion from `user_ns::ip_address` to a JSON string: 71/10000 · 71
3 :25
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — These `tag_invoke` overloads take an extra `as_string` parameter, which disambiguates this specific representation of `ip_address` from all other potential representations. In order to take advantage of them one needs to pass an `as_string` object to <<ref_value_from>> or <<ref_value_to>> as the last argument: 311/10000 · 311
4 :36
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Note, that if there is no dedicated `tag_invoke` overload for a given type and a given context, the implementation falls back to overloads without context. Thus it is easy to combine contextual conversions with conversions provided by the library: 247/10000 · 247
5 :46
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Conversions for Third-Party Types 33/10000 · 33
6 :47
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Normally, you wouldn't be able to provide conversions for types from third-party libraries and standard types, because it would require yout to put `tag_invoke` overloads into namespaces you do not control. But with contexts you can put the overloads into your namespaces. This is because the context will add its associated namespaces into the list of namespaces where `tag_invoke` overloads are searched. 406/10000 · 406
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