msgid "" msgstr "" "Project-Id-Version: English (Boost Json Translation (zh_Hans))\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2026-06-06 21:31+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: English \n" "Language: en\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Generator: Weblate 2026.5\n" #: :10 #, read-only, safe-html, strict-same msgid "" "= Custom Conversions Boost.JSON uses two mechanisms to customize conversion " "between <> and user types. One mechanism involves specializing " "type traits. The other one is more powerful and requires defining overloads " "of `tag_invoke`. Both mechanisms will be further explained in this section." msgstr "" "= Custom Conversions Boost.JSON uses two mechanisms to customize conversion " "between <> and user types. One mechanism involves specializing " "type traits. The other one is more powerful and requires defining overloads " "of `tag_invoke`. Both mechanisms will be further explained in this section." #: :16 #, read-only, safe-html, strict-same msgid "Conversion Traits" msgstr "Conversion Traits" #: :17 #, read-only, safe-html, strict-same msgid "" "Previously a number of conversion type traits, like <> or " "<>, were introduced. The library tries the traits one " "after another and uses the implementation that corresponds to the first " "matching trait. In some cases, though, a type would match a trait with a " "higher priority, but the user intends for it to belong to a lower priority " "category. If this happens the user can specialize the trait that's not " "supposed to match for that type to be an equivalent of `std::false_type`." msgstr "" "Previously a number of conversion type traits, like <> or " "<>, were introduced. The library tries the traits one " "after another and uses the implementation that corresponds to the first " "matching trait. In some cases, though, a type would match a trait with a " "higher priority, but the user intends for it to belong to a lower priority " "category. If this happens the user can specialize the trait that's not " "supposed to match for that type to be an equivalent of `std::false_type`." #: :25 #, read-only, safe-html, strict-same msgid "Consider this type:" msgstr "Consider this type:" #: :32 #, read-only, safe-html, strict-same msgid "" "It exposes both a sequence API and a tuple API. But converting from " "<> to `user_ns::ip_address` would not be able to use " "implementation for sequences, since those are constructed empty and then " "populated one element at a time, while `ip_address` has a fixed size of 4. " "The tuple conversion would fit, though. The only problem is that " "<> has a lower priority than <>. In " "order to circumvent this, the user only needs to specialize " "<> to not match `ip_address`." msgstr "" "It exposes both a sequence API and a tuple API. But converting from " "<> to `user_ns::ip_address` would not be able to use " "implementation for sequences, since those are constructed empty and then " "populated one element at a time, while `ip_address` has a fixed size of 4. " "The tuple conversion would fit, though. The only problem is that " "<> has a lower priority than <>. In " "order to circumvent this, the user only needs to specialize " "<> to not match `ip_address`." #: :45 #, read-only, safe-html, strict-same msgid "`tag_invoke` Overloads" msgstr "`tag_invoke` Overloads" #: :46 #, read-only, safe-html, strict-same msgid "" "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:" msgstr "" "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:" #: :55 #, read-only, safe-html, strict-same msgid "discard candidates that are unrelated to that particular" msgstr "discard candidates that are unrelated to that particular" #: :56 #, read-only, safe-html, strict-same msgid "customization point, and" msgstr "customization point, and" #: :58 #, read-only, safe-html, strict-same msgid "" "embed the user-defined type into the arguments list (e.g. by using a tag type" msgstr "" "embed the user-defined type into the arguments list (e.g. by using a tag type" #: :59 #, read-only, safe-html, strict-same msgid "" "template such as `value_to_tag`) so that its http://eel.is/c++draft/" "basic.lookup.argdep#2[associated namespaces and entities] are examined when " "name lookup is performed." msgstr "" "template such as `value_to_tag`) so that its http://eel.is/c++draft/" "basic.lookup.argdep#2[associated namespaces and entities] are examined when " "name lookup is performed." #: :63 #, read-only, safe-html, strict-same msgid "" "This has the effect of finding user-provided `tag_invoke` overloads, even if " "they are declared (lexically) after the definition of the calling function." msgstr "" "This has the effect of finding user-provided `tag_invoke` overloads, even if " "they are declared (lexically) after the definition of the calling function." #: :66 #, read-only, safe-html, strict-same msgid "Overloads of `tag_invoke` called by <> take the form:" msgstr "Overloads of `tag_invoke` called by <> take the form:" #: :68 #, read-only, safe-html, strict-same msgid "``` void tag_invoke( const value_from_tag&, value&, T ); ```" msgstr "``` void tag_invoke( const value_from_tag&, value&, T ); ```" #: :72 #, read-only, safe-html, strict-same msgid "" "While overloads of `tag_invoke` called by <> take the form:" msgstr "" "While overloads of `tag_invoke` called by <> take the form:" #: :74 #, read-only, safe-html, strict-same msgid "``` T tag_invoke( const value_to_tag< T >&, const value& ); ```" msgstr "``` T tag_invoke( const value_to_tag< T >&, const value& ); ```" #: :78 #, read-only, safe-html, strict-same msgid "" "If we implemented conversion for `user_ns::ip_address` manually with this " "approach, it would look like this:" msgstr "" "If we implemented conversion for `user_ns::ip_address` manually with this " "approach, it would look like this:" #: :86 #, read-only, safe-html, strict-same msgid "" "Since the type being converted is embedded into the function's signature, " "user-provided overloads are visible to argument-dependent lookup and will be " "candidates when a conversion is performed:" msgstr "" "Since the type being converted is embedded into the function's signature, " "user-provided overloads are visible to argument-dependent lookup and will be " "candidates when a conversion is performed:" #: :95 #, read-only, safe-html, strict-same msgid "" "Users can freely combine types with custom conversions with types with " "library-provided conversions. The library handles them correctly:" msgstr "" "Users can freely combine types with custom conversions with types with " "library-provided conversions. The library handles them correctly:"