Exit Zen
2
:19
English
The elements are stored contiguously as instances of <<ref_key_value_pair>>.
64/760 · 76
2
:17
English
There's no non-throwing equivalent for <<ref_value_from>>. This is simply because we haven't yet encountered a situation where <<ref_value_from>> needed to communicate an error to the caller.
127/1910 · 191
2
:21
English
Note that <<ref_value_from>> is declared using an out-parameter, rather then returning its result. This overload is specifically designed for this use-case.
82/1560 · 156
2
:17
English
<<ref_value_to>> does not have a similar parameter, as <<ref_value>> is not created.
91/840 · 84
2
:19
English
An empty array may be constructed without incurring any memory allocations using the <<default_memory_resource,default memory resource>>. A <<ref_storage_ptr>> can also be explicitly specified:
177/1930 · 193
2
:13
English
Serialization is the process where a JSON document represented in memory by a <<ref_value>> is turned into a sequence of characters. The library provides the following free functions and types for serialization:
81/2110 · 211
2
:19
English
Simple initializer lists produce an <<ref_array>>:
46/500 · 50
2
:18
English
The function template <<ref_value_from>> provides an interface to construct a <<ref_value>> from a type `T`. The function template <<ref_value_to>> converts in the opposite direction, from a type `T` to <<ref_value>>. Both support a wide variety of different https://en.cppreference.com/w/cpp/language/types[fundamental types], such as `int` or `double`, standard library types, such as `std::string` or `std::vector<T>`, and can be extended to support user-defined types.
341/4720 · 472
3
:18
English
The interface and functionality of <<ref_string>> is the same as {std_string} except that:
65/900 · 90
3
:36
English
In cases where you know that a <<ref_value>> contains a number but don't know its <<ref_kind>>, `value::to_number` can be used to convert the <<ref_value>> to an arithmetic type:
142/1780 · 178
3
:25
English
These `tag_invoke` overloads take an extra `as_string` parameter, which disambiguates this specific representation of `ip_address` from all other potential representations. In order to take advantage of them one needs to pass an `as_string` object to <<ref_value_from>> or <<ref_value_to>> as the last argument:
196/3110 · 311
3
:17
English
Previously a number of conversion type traits, like <<ref_is_tuple_like>> or <<ref_is_sequence_like>>, were introduced. The library tries the traits one after another and uses the implementation that corresponds to the first matching trait. In some cases, though, a type would match a trait with a higher priority, but the user intends for it to belong to a lower priority category. If this happens the user can specialize the trait that's not supposed to match for that type to be an equivalent of `std::false_type`.
253/5180 · 518
3
:23
English
That being said, if your types are default-constructible and you don't need the customisability allowed by <<ref_value_to>> and <<ref_value_from>>, then you can get a significant performance boost with direct conversions.
137/2210 · 221
3
:21
English
Iterators are ordinary pointers, and may become invalidated on insertions
24/730 · 73
3
:21
English
The library provides non-throwing conversions for all the categories of types it supports with <<ref_value_to>>. If a user wants to use it with custom types, an overload of `tag_invoke` of this form needs to be provided:
107/2200 · 220
3
:24
English
After that the definitions of `tag_invoke` overloads should be provided. These overloads have to be templates, since <<ref_value>> is only forward-declared and hence is an incomplete type.
89/1880 · 188
3
:20
English
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.
135/2430 · 243
4
:36
English
The library also allows changing and adding deeply nested elements. The function <<ref_value_set_at_pointer>> traverses the value similarly to <<ref_value_at_pointer>>, but additionally, it can create missing elements in certain cases:
166/2350 · 235
4
:45
English
If the <<ref_value>> does not contain a number, or if the conversion is to an integer type `T` and the number cannot be represented exactly by `T`, the conversion will fail. Otherwise, the result is the number converted to `T` as-if by `static_cast`:
110/2500 · 250
4
:27
English
Direct parsing is performed by the <<ref_parse_into>> family of functions. The library provides overloads that take either <<ref_string_view>> or `std::istream`, and can report errors either via throwing exceptions or setting an error code.
151/2400 · 240