Exit Zen
11
:53
English
The class template {ref_polymorphic_allocator} wraps a {ref_memory_resource} pointer and meets the requirements of {req_Allocator}, allowing it to be used where an allocator is expected. The standard provides type aliases using the polymorphic allocator for standard containers:
117/2780 · 278
11
:78
English
<<ref_has_value_from>> + <<ref_has_value_to>> + <<ref_is_deallocate_trivial>> + <<ref_is_described_class>> + <<ref_is_described_enum>> + <<ref_is_map_like>> + <<ref_is_null_like>> + <<ref_is_optional_like>> + <<ref_is_path_like>> + <<ref_is_sequence_like>> + <<ref_is_string_like>> + <<ref_is_tuple_like>> + <<ref_is_variant_like>> + <<ref_result_for>> + <<ref_try_value_to_tag>> + <<ref_value_from_tag>> + <<ref_value_to_tag>>
891/4270 · 427
11
:31
English
a <<ref_value>>.
12/160 · 16
11
:120
English
When a library type is used as the element type of a PMR container; that is, a container which uses a {ref_polymorphic_allocator}, the memory resource will automatically propagate to the type and all of its children:
78/2160 · 216
:39
:39
English
Parses the input using an instance of
16/370 · 37
11
:63
English
{icon_bad} Poor separation of concerns. The `basic_json` container
34/660 · 66
11
:29
English
<<ref_serializer>>
41/180 · 18
11
:100
English
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.
180/1830 · 183
:36
:36
English
The result is equal to the input value.
8/390 · 39
12
:13
English
https://drone.cpp.al/boostorg/json[image:https://drone.cpp.al/api/badges/boostorg/json/status.svg?ref=refs/heads/master[Build
122/1250 · 125
12
:34
English
the string holds only valid UTF-8.
21/340 · 34
12
:30
English
With augmented interface, operations requiring an input string are implemented as a single overload with a parameter of type <<ref_string_view>>, and can accept most string-like objects. Objects such as null terminated character pointers, `std::string`, <<ref_string>>, subranges of strings, and objects convertible to <<ref_string_view>> can all be passed to these functions.
229/3760 · 376
12
:83
English
then its type is `double`. Otherwise, if the number is positive and its value is greater than `INT64_MAX`, then its type is `std::uint64_t`. All other numbers are parsed as `std::int64_t`.
87/1880 · 188
12
:77
English
Contexts we used so far were empty classes. But contexts may have data members and member functions just as any class. Implementers of conversion functions can take advantage of that to have conversions configurable at runtime or pass special objects to conversions (e.g. allocators).
93/2840 · 284
12
:63
English
This has the effect of finding user-provided `tag_invoke` overloads, even if they are declared (lexically) after the definition of the calling function.
59/1520 · 152
12
:64
English
Internally, the container computes a hash table over the keys so that the complexity of lookups is in constant time, on average.
41/1280 · 128
12
:38
English
A <<ref_value>> constructed from `nullptr` or default constructed represents a null JSON element:
64/970 · 97
12
:37
English
This lists all of the allocation-related types and functions available when using the library:
29/940 · 94
12
:63
English
A polymorphic allocator constructs with a pointer to a memory resource:
23/710 · 71
12
:98
English
include::{entities-file}[leveloffset=+1]
40/400 · 40