User avatar admin

Translation uploaded
{ref_polymorphic_allocator} do not acquire ownership; the caller is responsible for ensuring that the lifetime of the resource extends until it is no longer referenced.
从 {ref_polymorphic_allocator} do not acquire ownership; the caller is responsible for ensuring that the lifetime of the resource extends until it is no longer referenced.构造的存储指针，不获取所有权；调用方负责确保资源的生命周期持续到不再被引用为止。
06/05/2026
User avatar admin

Translation uploaded
Storage pointers constructed from a {ref_memory_resource} or
Storage pointers constructed from a从 {ref_memory_resource} or构造的存储指针，或
06/05/2026
User avatar admin

Translation uploaded
<<default_memory_resource,default resource>>, an implementation-defined instance which always uses the equivalent of global operator new and delete.
<&lt;<default_memory_resource,default resource>>, an implementation-defined instance which always uses the equivalent of global operator new and delete.="">&gt;（默认资源），这是一个由实现定义的实例，始终使用等效于全局 operator new 和 operator delete 的方式。</default_memory_resource,default>
06/05/2026
User avatar admin

Translation uploaded
Default-constructed storage pointers reference the
Default-constructed storage pointers reference the默认构造的存储指针引用
06/05/2026
User avatar admin

Translation uploaded
type-erased {ref_memory_resource}.
type-erased类型擦除后的 {ref_memory_resource}.。
06/05/2026
User avatar admin

Translation uploaded
A storage pointer always points to a valid,
A storage pointer always points to a valid,存储指针始终指向一个有效的、
06/05/2026
User avatar admin

Translation uploaded
= `storage_ptr` Variable-length containers in this library all use dynamically allocated memory to store their contents. Callers can gain control over the strategy used for allocation by specifying a <<ref_storage_ptr>> in select constructors and function parameter lists. A <<ref_storage_ptr>> has these properties:
= `storage_ptr` Variable-length containers in this library all use dynamically allocated memory to store their contents. Callers can gain control over the strategy used for allocation by specifying a <<ref_storage_ptr>> in select constructors and function parameter lists. A <<ref_storage_ptr>> has these properties:本库中的可变长度容器均使用动态分配的内存来存储其内容。调用方可通过在特定构造函数和函数参数列表中指定 &lt;<ref_storage_ptr>&gt; ，以控制所使用的内存分配策略。&lt;<ref_storage_ptr>&gt; 具有以下特性：</ref_storage_ptr></ref_storage_ptr>
06/05/2026
User avatar admin

Resource updated
File “doc/pages/allocators/storage_ptr_zh_Hans.adoc” was added. 06/05/2026
User avatar admin

String added in the repository
To implement custom memory allocation strategies, derive your class from {ref_memory_resource} and implement the functions `do_allocate`, `do_deallocate`, and `do_is_equal` as seen in this example below, which logs each operation it performs to the console:
To implement custom memory allocation strategies, derive your class from {ref_memory_resource} and implement the functions `do_allocate`, `do_deallocate`, and `do_is_equal` as seen in this example below, which logs each operation it performs to the console:
06/05/2026
User avatar admin

String added in the repository
User-Defined Resource
User-Defined Resource
06/05/2026
User avatar admin

String added in the repository
When a storage pointer is constructed this way, the lifetime of the referenced memory resource is extended until all variables which reference it are destroyed.
When a storage pointer is constructed this way, the lifetime of the referenced memory resource is extended until all variables which reference it are destroyed.
06/05/2026
User avatar admin

String added in the repository
Shared ownership is achieved using the function <<ref_make_shared_resource>>, which creates a new, reference-counted memory resource using a dynamic memory allocation and returns it as a <<ref_storage_ptr>>:
Shared ownership is achieved using the function <<ref_make_shared_resource>>, which creates a new, reference-counted memory resource using a dynamic memory allocation and returns it as a <<ref_storage_ptr>>:
06/05/2026
User avatar admin

String added in the repository
When using a memory resource in this fashion, including the case where a storage pointer or container is constructed from a {ref_polymorphic_allocator}, the caller must ensure that the lifetime of the resource is extended until it is no longer referenced by any variables; otherwise, undefined behavior is possible.
When using a memory resource in this fashion, including the case where a storage pointer or container is constructed from a {ref_polymorphic_allocator}, the caller must ensure that the lifetime of the resource is extended until it is no longer referenced by any variables; otherwise, undefined behavior is possible.
06/05/2026
User avatar admin

String added in the repository
It is important to note that <<ref_storage_ptr>> supports both shared-ownership and reference lifetime models. Construction from a memory resource pointer does not transfer ownership:
It is important to note that <<ref_storage_ptr>> supports both shared-ownership and reference lifetime models. Construction from a memory resource pointer does not transfer ownership:
06/05/2026
User avatar admin

String added in the repository
Resource Lifetime
Resource Lifetime
06/05/2026
User avatar admin

String added in the repository
This propagation acts recursively, containers within containers will all have the resource propagated. Once a container is constructed, its memory resource can never be changed.
This propagation acts recursively, containers within containers will all have the resource propagated. Once a container is constructed, its memory resource can never be changed.
06/05/2026
User avatar admin

String added in the repository
The containers <<ref_array>>, <<ref_object>>, and <<ref_value>> all propagate the memory resource they were constructed with to child elements:
The containers <<ref_array>>, <<ref_object>>, and <<ref_value>> all propagate the memory resource they were constructed with to child elements:
06/05/2026
User avatar admin

String added in the repository
Allocator Propagation
Allocator Propagation
06/05/2026
User avatar admin

String added in the repository
The function <<ref_get_null_resource>> returns a global instance of the null resource. This resource offers a simple invariant: all calls to allocate will throw the exception `std::bad_alloc`. An instance of the null resource can be used to make parsing guarantee that allocations from the heap are never made. This is explored in more detail in a later section.
The function <<ref_get_null_resource>> returns a global instance of the null resource. This resource offers a simple invariant: all calls to allocate will throw the exception `std::bad_alloc`. An instance of the null resource can be used to make parsing guarantee that allocations from the heap are never made. This is explored in more detail in a later section.
06/05/2026
User avatar admin

String added in the repository
Null Resource
Null Resource
06/05/2026

Search