2. Boost Json Translation (zh_Hans)
3. Doc / Pages / Allocators / Storage Ptr (adoc)
4. English
5. Zen

50 :151
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 312/10000 · 312
51 :157
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To use the resource, construct it with a local buffer: 54/10000 · 54
52 :164
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Null Resource 13/10000 · 13
53 :165
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 362/10000 · 362
54 :171
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Allocator Propagation 21/10000 · 21
55 :172
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The containers <<ref_array>>, <<ref_object>>, and <<ref_value>> all propagate the memory resource they were constructed with to child elements: 143/10000 · 143
56 :180
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 177/10000 · 177
57 :184
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Resource Lifetime 17/10000 · 17
58 :185
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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: 183/10000 · 183
59 :194
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 315/10000 · 315
60 :200
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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>>: 207/10000 · 207
61 :209
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 160/10000 · 160
62 :213
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — User-Defined Resource 21/10000 · 21
63 :214
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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: 257/10000 · 257
The translation has come to an end.