User avatar admin

Translation uploaded
In settings where exceptions cannot be used, an overload of `value::to_number` accepting {ref_error_code} can be used instead with identical semantics to its throwing counterpart:
In settings where exceptions cannot be used, an overload of `value::to_number` accepting {ref_error_code} can be used instead with identical semantics to its throwing counterpart:在无法使用异常的场合，可改用接受{ref_error_code}的`value::to_number`重载，其语义与抛出异常版本完全相同：
06/05/2026
User avatar admin

Translation uploaded
If the <<ref_value>> does not contain a number, or if the conversion is to an integer type `T` and the number cannot be represented exactly by `T`, the conversion will fail. Otherwise, the result is the number converted to `T` as-if by `static_cast`:
If the <若&lt;<ref_value>> does not contain a number, or if the conversion is to an integer type `T` and the number cannot be represented exactly by `T`, the conversion will fail. Otherwise, the result is the number converted to `T` as-if by `static_cast`:&gt;不包含数字，或当转换目标为整数类型`T`且数字无法被`T`精确表示时，将导致转换失败。否则，结果是通过`static_cast`将数字转换为`T`所得的值：</ref_value>
06/05/2026
User avatar admin

Translation uploaded
In cases where you know that a <<ref_value>> contains a number but don't know its <<ref_kind>>, `value::to_number` can be used to convert the <<ref_value>> to an arithmetic type:
In cases where you know that a <<ref_value>> contains a number but don't know its <若已知 &lt;<ref_value>&gt; 包含数字，但不确定其 &lt;<ref_kind>>,&gt;，可使用 `value::to_number` can be used to convert the <<ref_value>> to an arithmetic type:将该&lt;<ref_value>&gt; 转换为算术类型：</ref_value></ref_kind></ref_value>
06/05/2026
User avatar admin

Translation uploaded
When accessing a number contained within a <<ref_value>>, the function used must match the value's <<ref_kind>> exactly; no conversions will be performed. For example if `as_double` is called on a <<ref_value>> that contains a `std::uint64_t`, an exception is thrown. Similarly, the function `if_double` will return `nullptr` and calling `get_double` will result in undefined behavior:
When accessing a number contained within a <<ref_value>>, the function used must match the value's <<ref_kind>> exactly; no conversions will be performed. For example if `as_double` is called on a <<ref_value>> that contains a `std::uint64_t`, an exception is thrown. Similarly, the function `if_double` will return `nullptr` and calling `get_double` will result in undefined behavior:访问&lt;<ref_value>&gt;内包含的数字时，所使用的函数必须与该值的&lt;<ref_kind>&gt;完全匹配；不会执行任何转换。例如，如果在一个包含`std::uint64_t` 的 &lt;<ref_value>&gt; 上调用 `as_double`，将抛出异常。类似地，函数 `if_double` 将返回`nullptr`，而调用 `get_double` 将导致未定义行为：</ref_value></ref_kind></ref_value>
06/05/2026
User avatar admin

Translation uploaded
= Numbers JSON numbers are represented using `std::int64_t`, `std::uint64_t`, and `double`. When a <<ref_value>> is constructed from an unsigned integer, its <<ref_kind>> will be `kind::uint64`. Likewise, a <<ref_value>> constructed from a signed integer will have `kind::int64`, or `kind::double_` if constructed from a floating-point type:
= Numbers JSON numbers are represented using 数字 JSON数字使用`std::int64_t`, 、`std::uint64_t`, and 和`double`. When a <表示。当 &lt;<ref_value>> is constructed from an unsigned integer, its <<ref_kind>> will be `kind::uint64`. Likewise, a <<ref_value>> constructed from a signed integer will have &gt; 从无符号整数构造时，其&lt;<ref_kind>&gt;将为`kind::uint64`。同样，从有符号整数构造的&lt;<ref_value>&gt; 将具有`kind::int64`, or ，若从浮点类型构造则为`kind::double_` if constructed from a floating-point type:：</ref_value></ref_kind></ref_value>
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
The specific behavior is controlled by an optional parameter of type <<ref_set_pointer_options>>. For example, here's the same example with a different option:
The specific behavior is controlled by an optional parameter of type <<ref_set_pointer_options>>. For example, here's the same example with a different 具体行为由一个类型为 &lt;<ref_set_pointer_options>&gt; 的可选参数控制。例如，以下是使用不同选项的相同示例：</ref_set_pointer_option:s>
06/05/2026
User avatar admin

Translation uploaded
The library also allows changing and adding deeply nested elements. The function <<ref_value_set_at_pointer>> traverses the value similarly to <<ref_value_at_pointer>>, but additionally, it can create missing elements in certain cases:
The library also allows changing and adding deeply nested elements. The function <<ref_value_set_at_pointer>> traverses the value similarly to <<ref_value_at_pointer>>, but additionally, it can create missing elements in certain cases:该库还支持修改和添加深层嵌套的元素。函数 &lt;<ref_value_set_at_pointer>&gt; 以与 &lt;<ref_value_at_pointer>&gt; 类似的方式遍历值，但在某些情况下还能创建缺失的元素：</ref_value_at_pointer></ref_value_set_at_pointer>
06/05/2026
User avatar admin

Translation uploaded
with
with与
06/05/2026
User avatar admin

Translation uploaded
This is particularly useful when throwing exceptions is undesirable. For example, compare
This is particularly useful when throwing exceptions is undesirable. For example, compare这在不希望抛出异常的场景中尤为有用。例如，对比以下两种方式：
06/05/2026
User avatar admin

Translation uploaded
= Accessing Deeply Nested Elements In order to allow conveniently retrieving and changing deeply nested elements of <<ref_value>> objects the library implements https://datatracker.ietf.org/doc/html/rfc6901[RFC 6901 (JSON Pointer)]:
= Accessing Deeply Nested Elements In order to allow conveniently retrieving and changing deeply nested elements of <<ref_value>> objects the library implements访问深层嵌套元素 为了便于便捷地获取和修改 &lt;<ref_value>&gt; 对象中深层嵌套的元素，该库实现了 https://datatracker.ietf.org/doc/html/rfc6901[RFC 6901 (JSON Pointer)]:</ref_value>
06/05/2026
User avatar admin

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

Translation uploaded
In all cases, the <<ref_storage_ptr>> owned by an <<ref_object>>, <<ref_array>>, or <<ref_value>> constructed from an initializer list will be propagated to each element, recursively.
In all cases, the <<ref_storage_ptr>> owned by an <在所有情况下，通过初始化列表构造的 &lt;<ref_object>>, <&gt;、&lt;<ref_array>>, or <<ref_value>> constructed from an initializer list will be propagated to each element, recursively.&gt; 或 &lt;<ref_value>&gt; 所拥有的 &lt;<ref_storage_ptr>&gt; 都会递归地传播到每个元素。</ref_storage_ptr></ref_value></ref_array></ref_object>
06/05/2026
User avatar admin

Translation uploaded
Elements that are rvalues will be moved upon initialization:
Elements that are rvalues will be moved upon initialization:在初始化时，右值元素将被移动。
06/05/2026
User avatar admin

Translation uploaded
The requirement for an initializer list to be interpreted as an <<ref_object>> or <<ref_array>> when initializing such an entity only applies to the outermost initializer list; subsequent nested elements will follow the usual ambiguity resolution rules.
The requirement for an initializer list to be interpreted as an <<ref_object>> or <<ref_array>> when initializing such an entity only applies to the outermost initializer list; subsequent nested elements will follow the usual ambiguity resolution rules.当初始化一个 &lt;<ref_object>&gt; 或 &lt;<ref_array>&gt; 时，要求初始化列表被解释为对应类型的规则仅适用于最外层的初始化列表；后续嵌套的元素将遵循常规的歧义解析规则。</ref_array></ref_object>
06/05/2026
User avatar admin

Translation uploaded
Similarly, an initializer list for an <<ref_object>> is always interpreted as an <<ref_object>>. In such cases, the initializer list must be a list of key-value pairs. For example, the following code will not compile because `1` is not convertible to a string:
Similarly, an initializer list for an <<ref_object>> is always interpreted as an <<ref_object>>. In such cases, the initializer list must be a list of key-value pairs. For example, the following code will not compile because `1` is not convertible to a string:同样，用于 &lt;<ref_object>&gt; 的初始化列表始终会被解释为 &lt;<ref_object>&gt;。此时，初始化列表必须由键值对组成。例如，以下代码无法编译，因为` `1 无法转换为字符串：</ref_object></ref_object>
06/05/2026
User avatar admin

Translation uploaded
Initializer lists can be used to unambiguously construct or assign an <<ref_object>> or <<ref_array>>:
Initializer lists can be used to unambiguously construct or assign an <<ref_object>> or <<ref_array>>:初始化列表可用于明确地构造或赋值一个&lt;<ref_object>&gt; 或 &lt;<ref_array>&gt;：</ref_array></ref_object>
06/05/2026
User avatar admin

Translation uploaded
To resolve the ambiguity manually, use an explicit constructor:
To resolve the ambiguity manually, use an explicit constructor:要手动消除歧义，请使用显式构造函数：
06/05/2026
User avatar admin

Translation uploaded
In such cases, if every element consists of a string followed by a single value, then the enclosing initializer list is interpreted as an <<ref_object>>. Otherwise, it is interpreted as an <<ref_array>>.
In such cases, if every element consists of a string followed by a single value, then the enclosing initializer list is interpreted as an <<ref_object>>. Otherwise, it is interpreted as an <<ref_array>>.在这种情况下，如果每个元素均由一个字符串后跟一个值组成，则外层的初始化列表会被解释为一个 &lt;<ref_object>&gt;；否则，它会被解释为一个 &lt;<ref_array>&gt;。</ref_array></ref_object>
06/05/2026
User avatar admin

Translation uploaded
When a two element initializer list is nested within an enclosing initializer list, it is unclear whether it represents an <<ref_array>> or an <<ref_object>>:
When a two element initializer list is nested within an enclosing initializer list, it is unclear whether it represents an <<ref_array>> or an <<ref_object>>:当一个包含两个元素的初始化列表嵌套在外部初始化列表中时，尚不明确它表示的是一个 &lt;<ref_array>&gt; 还是一个 &lt;<ref_object>&gt;：</ref_object></ref_array>
06/05/2026

Search