The translation has come to an end.
Exit Zen
1
:11
English
= `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:
177/3160 · 316
5
:21
English
<<default_memory_resource,default resource>>, an implementation-defined instance which always uses the equivalent of global operator new and delete.
152/1480 · 148
13
:41
English
Name
4/100 · 4
24
:57
English
{ref_memory_resource}
21/210 · 21
29
:66
English
{ref_polymorphic_allocator}
27/270 · 27
36
:75
English
A smart pointer through which a {ref_memory_resource} is managed and
68/680 · 68
39
:81
English
The default memory resource uses the global `operator new` and `operator delete` to allocate memory. This resource is not reference counted and has a non-trivial deallocate function. All default-constructed <<ref_storage_ptr>> objects reference the same memory resource:
152/2700 · 270
45
:116
English
The <<ref_monotonic_resource>> optimizes this memory allocation pattern by allocating increasingly large blocks of global memory internally and parceling those blocks out in smaller pieces to fulfill allocation requests. It has a trivial deallocate function. The monotonic resource does not actually deallocate memory until the resource is destroyed. Thus, it is ideally suited for the use-case where JSON is parsed, and the resulting value is then inspected but not modified.
187/4760 · 476
46
:124
English
The resource to use when constructing values may be specified in calls to <<ref_parse>> as shown here:
58/1020 · 102
50
:151
English
A <<ref_static_resource>> constructs from a caller-provided buffer, and satisfies all memory allocation requests from the buffer. Once the buffer is exhausted, subsequent calls to allocate throw the exception `std::bad_alloc`. The resource offers a simple invariant: dynamic heap allocations are never performed.
147/3120 · 312
53
:165
English
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.
162/3620 · 362
55
:172
English
The containers <<ref_array>>, <<ref_object>>, and <<ref_value>> all propagate the memory resource they were constructed with to child elements:
127/1430 · 143
58
:185
English
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:
88/1830 · 183
60
:200
English
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>>:
160/2070 · 207
The translation has come to an end.