User avatar admin

Translation uploaded
If library-provided conversions are suitable for you, you have the option to use direct conversions. This also puts the requirement of being default constructible on many of your types.
If library-provided conversions are suitable for you, you have the option to use direct conversions. This also puts the requirement of being default constructible on many of your types.如果库提供的转换对你适用，你可以选择使用直接转换。但这同时也要求你的许多类型必须是可默认构造的。
06/05/2026
User avatar admin

Translation uploaded
The first advice is to use one of the library-provided conversions, rather then providing a custom one, unless the resulting format is undesirable. If the library deduces the wrong conversion category, you can opt out by specialising the relevant trait to inherit from `std::false_type`.
The first advice is to use one of the library-provided conversions, rather then providing a custom one, unless the resulting format is undesirable. If the library deduces the wrong conversion category, you can opt out by specialising the relevant trait to inherit from首要建议是：除非生成的格式不符合需求，否则应优先使用库提供的转换，而非自行实现自定义转换。如果库错误地推断了转换类别，你可以通过将相关特征特化为继承自 `std::false_type`. 来排除该转换。
06/05/2026
User avatar admin

Translation uploaded
= Conversion Customization Guidelines With so many options, it can be hard to choose the best way to customise conversion for your type. In this section, we will discuss those options and suggest which to choose when.
= Conversion Customization Guidelines With so many options, it can be hard to choose the best way to customise conversion for your type. In this section, we will discuss those options and suggest which to choose when.转换自定义指南 由于选项众多，为类型选择最合适的转换自定义方式可能并不容易。本节将讨论这些选项，并给出不同场景下的选用建议。
06/05/2026
User avatar admin

File uploaded
Processed 5 strings from the uploaded files (skipped: 0, not found: 0, updated: 5).
File upload mode: Add as translation 06/05/2026
User avatar admin

Translation uploaded
Forward declarations of contextual conversions are done very similarly:
Forward declarations of contextual conversions are done very similarly:上下文相关转换的前向声明方式与此非常相似：
06/05/2026
User avatar admin

Translation uploaded
As discussed previously, we prefer to define a non-throwing overload of `tag_invoke` for <<ref_try_value_to>>, rather then the throwing overload for <<ref_value_to>>, as the latter can fallback to the former without performance degradation.
As discussed previously, we prefer to define a non-throwing overload of `tag_invoke` for <<ref_try_value_to>>, rather then the throwing overload for <<ref_value_to>>, as the latter can fallback to the former without performance degradation.如前所述，我们更倾向于为 &lt;<ref_try_value_to>&gt; 定义不抛异常的 `tag_invoke` 重载，而不是为 &lt;<ref_value_to>&gt; 定义抛异常的重载，因为后者可以在无性能损失的情况下回退到前者。</ref_value_to></ref_try_value_to>
06/05/2026
User avatar admin

Translation uploaded
After that the definitions of `tag_invoke` overloads should be provided. These overloads have to be templates, since <<ref_value>> is only forward-declared and hence is an incomplete type.
After that the definitions of `tag_invoke` overloads should be provided. These overloads have to be templates, since <<ref_value>> is only forward-declared and hence is an incomplete type.之后应提供 `tag_invoke` 重载的定义。这些重载必须是模板，因为 &lt;<ref_value>&gt; 仅是前向声明的，因此是一个不完整类型。</ref_value>
06/05/2026
User avatar admin

Translation uploaded
Note that <<ref_value_from>> is declared using an out-parameter, rather then returning its result. This overload is specifically designed for this use-case.
Note that <请注意，&lt;<ref_value_from>> is declared using an out-parameter, rather then returning its result. This overload is specifically designed for this use-case.&gt; 是通过输出参数声明的，而非返回其结果。该重载正是为这一使用场景而设计的。</ref_value_from>
06/05/2026
User avatar admin

Translation uploaded
= Avoiding Physical Dependency Some users, particularly library authors, may wish to provide conversions between their types and <<ref_value>>, but at the same time would prefer to avoid having their library depend on Boost.JSON. This is possible to achieve with the help of a few forward declarations.
= Avoiding Physical Dependency Some users, particularly library authors, may wish to provide conversions between their types and <<ref_value>>, but at the same time would prefer to avoid having their library depend on Boost.JSON. This is possible to achieve with the help of a few forward declarations.避免物理依赖 一些用户（尤其是库作者）可能希望为其类型与 &lt;<ref_value>&gt; 提供转换功能，但同时又希望避免让自己的库依赖 Boost.JSON。借助一些前向声明，即可实现这一目标。</ref_value>
06/05/2026
User avatar admin

File uploaded
Processed 6 strings from the uploaded files (skipped: 0, not found: 0, updated: 6).
File upload mode: Add as translation 06/05/2026
User avatar admin

Translation uploaded
Direct serialization doesn't require any special components and works with the regular <<ref_serializer>> and <<ref_serialize>>.
Direct serialization doesn't require any special components and works with the regular <<直接序列化不需要任何特殊组件，可直接使用常规的 &lt;<ref_serializer>&gt; 和&lt;<ref_serialize>&gt;。</ref_serializer>> and <<></ref_serializer>>.
06/05/2026
User avatar admin

Translation uploaded
If you need to combine incremental parsing with direct parsing, you can resort to <<ref_parser_for>>. `parser_for<T>` is an instantiation of <<ref_basic_parser>> that parses into an object of type `T`, and is what <<ref_parse_into>> uses under the hood.
If you need to combine incremental parsing with direct parsing, you can resort to <如果需要将增量解析与直接解析结合使用，可以借助 &lt;<ref_parser_for>>. &gt;。`parser_for<T>` is an instantiation of <<ref_basic_parser>> that t>`是&lt;<ref_basic_parser>&gt; 的一个实例化，用于将数据解析到类型为`T`的对象中，并且是&lt;<ref_parses _into an object of type `T`, and is what <<ref_parse_into>> uses under the hood.>&gt;在底层所使用的。</ref_parse_into></ref_basic_parser></t></ref_parser_for>
06/05/2026
User avatar admin

Translation uploaded
Direct parsing is performed by the <<ref_parse_into>> family of functions. The library provides overloads that take either <<ref_string_view>> or `std::istream`, and can report errors either via throwing exceptions or setting an error code.
Direct parsing is performed by the <<ref_parse_into>> family of functions. The library provides overloads that take either <直接解析是由&lt;<ref_parse_into>&gt; 系列函数执行的。库提供了接受&lt;&lt;<ref_string_view>> or &gt; 或`std::istream`, and can report errors either via throwing exceptions or setting an error code.的重载，并且可以通过抛出异常或设置错误码来报告错误。</ref_string_view></ref_parse_into>
06/05/2026
User avatar admin

Translation uploaded
That being said, if your types are default-constructible and you don't need the customisability allowed by <<ref_value_to>> and <<ref_value_from>>, then you can get a significant performance boost with direct conversions.
That being said, if your types are default-constructible and you don't need the customisability allowed by <<ref_value_to>> and <<ref_value_from>>, then you can get a significant performance boost with direct conversions.尽管如此，如果你的类型是可默认构造的，并且不需要 &lt;<ref_value_to>&gt; 和 &lt;<ref_value_from>&gt; 所提供的自定义能力，那么使用直接转换可以获得显著的性能提升。</ref_value_from></ref_value_to>
06/05/2026
User avatar admin

Translation uploaded
The drawback of this approach is that fully custom type representations are not supported, only the library-provided conversions are. Also all objects that should be populated by parsing have to be default constructible types. This includes not only the top-level object, but e.g. elements of containers, members of described `struct`s, and alternatives of variants.
The drawback of this approach is that fully custom type representations are not supported, only the library-provided conversions are. Also all objects that should be populated by parsing have to be default constructible types. This includes not only the top-level object, but e.g. elements of containers, members of described `struct`s, and alternatives of variants.这种方法的缺点在于，不支持完全自定义的类型表示，仅支持库提供的转换。此外，所有需通过解析进行填充的对象都必须是可默认构造的类型——这不仅包括顶层对象，也包括容器的元素、所描述`struct`的成员以及变体类型的备选项。
06/05/2026
User avatar admin

Translation uploaded
= Direct Conversion For large inputs parsing into the library's containers followed by conversion via <<ref_value_to>> (or vice versa <<ref_value_from>> followed by serialization from a <<ref_value>>) might be prohibitively expensive. For these cases the library provides components that allow parsing directly into and serializing directly from user-provided objects.
= Direct Conversion For large inputs parsing into the library's containers followed by conversion via <<ref_value_to>> (or vice versa <<ref_value_from>> followed by serialization from a <<ref_value>>) might be prohibitively expensive. For these cases the library provides components that allow parsing directly into and serializing directly from user-provided objects.直接转换 对于大型输入，先解析到库的容器中，再通过 &lt;<ref_value_to>&gt; 进行转换（或反之，先通过 &lt;<ref_value_from>&gt; 转换，再从 &lt;<ref_value>&gt; 序列化）可能代价过高。针对这类场景，库提供了可直接将数据解析到用户提供的对象中、或直接从用户提供的对象进行序列化的组件。</ref_value></ref_value_from></ref_value_to>
06/05/2026
User avatar admin

File uploaded
Processed 19 strings from the uploaded files (skipped: 0, not found: 0, updated: 19).
File upload mode: Add as translation 06/05/2026
User avatar admin

Translation uploaded
Users can freely combine types with custom conversions with types with library-provided conversions. The library handles them correctly:
Users can freely combine types with custom conversions with types with library-provided conversions. The library handles them correctly:用户可以自由地将具有自定义转换的类型与具有库提供转换的类型组合使用，库能正确处理它们：
06/05/2026
User avatar admin

Translation uploaded
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:
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:由于要转换的类型已嵌入到函数的签名中，因此用户自定义的重载形式会出现在依赖于参数的查找过程中，并且在进行转换时会成为候选选项：
06/05/2026
User avatar admin

Translation uploaded
If we implemented conversion for `user_ns::ip_address` manually with this approach, it would look like this:
If we implemented conversion for `user_ns::ip_address` manually with this approach, it would look like this:如果我们采用这种方式手动对 `user_ns::ip_address` 进行转换，其效果将会是这样的：
06/05/2026

Search