User avatar admin

Translation uploaded
This implementation explicitly creates an <<ref_array>> rather than relying on assignment from an initializer list. But the array uses default {ref_memory_resource}, not the one used by `jv`.
This implementation explicitly creates an <<ref_array>> rather than relying on assignment from an initializer list. But the array uses default {ref_memory_resource}, not the one used by `jv`.该实现显式创建了一个 &lt;<ref_array>&gt;，而不是依赖于初始化列表的赋值。但该数组使用的是默认的 {ref_memory_resource}，而不是`jv`所使用的内存资源。</ref_array>
06/05/2026
User avatar admin

Translation uploaded
``` void tag_invoke( const value_from_tag&, value& jv, ip_address const& addr ) { jv = array{ b[0], b[1], b[2], b[3] }; } ```
``` void tag_invoke( const value_from_tag&amp;, value&amp; jv, ip_address const&amp; addr ) { jv = array{ b[0], b[1], b[2], b[3] }; } ```
06/05/2026
User avatar admin

Translation uploaded
For example, consider this alternative implementation of `tag_invoke` for `ip_address` from the section <<custom_conversions>>.
For example, consider this alternative implementation of `tag_invoke` for `ip_address` from the section <<例如，考虑&lt;<custom_conversions>&gt;节中针对`ip_address`的`tag_invoke`的替代实现。</custom_conversions>>.
06/05/2026
User avatar admin

Translation uploaded
As the conversion result is set via an output parameter of type `value&`, the intended <<ref_storage_ptr>> is correctly propagated. But users still should take care to not create temporaries using the default {ref_memory_resource} by accident.
As the conversion result is set via an output parameter of type `value&`, the intended <<ref_storage_ptr>> is correctly propagated. But users still should take care to not create temporaries using the default {ref_memory_resource} by accident.由于转换结果是通过类型为`value&amp;`的输出参数设置的，因此预期的&lt;<ref_storage_ptr>&gt;会被正确传播。但用户仍需注意，避免意外创建使用默认 {ref_memory_resource} 的临时对象。</ref_storage_ptr>
06/05/2026
User avatar admin

Translation uploaded
<<ref_value_to>> does not have a similar parameter, as <<ref_value>> is not created.
<&lt;<ref_value_to>> does not have a similar parameter, as <<ref_value>> is not created.&gt; 没有类似的参数，因为该函数不会创建 &lt;<ref_value>&gt; 对象。</ref_value></ref_value_to>
06/05/2026
User avatar admin

Translation uploaded
= Allocation Control As <<ref_value_from>> creates a <<ref_value>> object, users may want to control the way memory is allocated for it. For this reason the function has an optional <<ref_storage_ptr>> parameter, that is used to set the {ref_memory_resource} for the result.
= Allocation Control As <<ref_value_from>> creates a <<ref_value>> object, users may want to control the way memory is allocated for it. For this 分配控制 由于&lt;<ref_value_from>&gt;会创建一个&lt;<ref_value>&gt;对象，用户可能希望控制其内存分配方式。因此，该函数具有一个可选的 &lt;<ref_storage_ptr>&gt; 参数，用于为结果指定{ref_memory_reason the function has an optional <<ref_storage_ptr>> parameter, that is used to set the {ref_memory_resource} for the result.urce}。</ref_storage_ptr></ref_value></ref_value_from>
06/05/2026
User avatar admin

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

Translation uploaded
{icon_good} The fastest available JSON parser.
{icon_good} The fastest available JSON parser.为目前最快的JSON解析器。
06/05/2026
User avatar admin

Translation uploaded
{icon_bad} Read-only, can only be populated by the provided SIMD JSON parser.
{icon_bad} Read-only, can only be populated by the provided为只读类型，仅能通过所提供的 SIMD JSON parser.解析器进行填充。
06/05/2026
User avatar admin

Translation uploaded
{icon_bad} Sequential access only, via `ParsedJson::BasicIterator`
{icon_bad} Sequential access only, via仅支持通过 `ParsedJson::BasicIterator` 进行顺序访问
06/05/2026
User avatar admin

Translation uploaded
This is quite an interesting data structure, which is optimized to work well with the SIMD parser. It makes very good design choices for the intended use-case. However it is not well suited as a vocabulary type due to the necessary limitations.
This is quite an interesting data structure, which is optimized to work well with the SIMD parser. It makes very good design choices for the intended use-case. However it is not well suited as a vocabulary type due to the necessary limitations.这是一种相当有趣的数据结构，专为与 SIMD 解析器协同工作而优化。它在目标使用场景下做出了非常优秀的设计选择。然而，由于其必要的限制，它不太适合作为通用类型。
06/05/2026
User avatar admin

Translation uploaded
Comparison to SIMD JSON
Comparison to 与SIMD JSON的比较
06/05/2026
User avatar admin

Translation uploaded
libraries.
libraries.库。
06/05/2026
User avatar admin

Translation uploaded
{icon_good} Parsing and serialization performance is better than most other
{icon_good} Parsing and serialization performance is better than most other解析和序列化性能优于大多数其他。
06/05/2026
User avatar admin

Translation uploaded
{icon_bad} No incremental parsing, no incremental serialization.
{icon_bad} No incremental parsing, no incremental serialization.没有增量式解析，也没有增量式序列化。
:106
06/05/2026
User avatar admin

Translation uploaded
different from their standard library equivalents, and not idiomatic.
different from their standard library equivalents, and not idiomatic.与标准库中的对应类型差异显著，且不符合惯用法。
06/05/2026
User avatar admin

Translation uploaded
{icon_bad} The interface of the array and object types are considerably
{icon_bad} The interface of the array and object types are considerably数组和对象类型的接口
06/05/2026
User avatar admin

Translation uploaded
easily encountered.
easily encountered.（容易引发。）
06/05/2026
User avatar admin

Translation uploaded
{icon_bad} Allocators have reference semantics. Problems with lifetime are
{icon_bad} Allocators have reference semantics. Problems with lifetime are分配器采用引用语义，容易引发生命周期问题。
06/05/2026
User avatar admin

Translation uploaded
lookups.
lookups.(查找。)
06/05/2026

Search