Exit Zen
4
:36
English
Category of T
13/130 · 13
5
:4
English
https://azure.microsoft.com/en-us/services/devops/pipelines/[Azure]
67/670 · 67
5
:46
English
The specific behavior is controlled by an optional parameter of type <<ref_set_pointer_options>>. For example, here's the same example with a different option:
97/1590 · 159
5
:18
English
A sequence container of JSON values supporting dynamic size and fast, random
28/760 · 76
5
:22
English
<<ref_string>> uses `char` as its character type,
50/490 · 49
5
:55
English
In settings where exceptions cannot be used, an overload of `value::to_number` accepting {ref_error_code} can be used instead with identical semantics to its throwing counterpart:
69/1790 · 179
5
:30
English
If your users are external, they and not you decide whether throwing exceptions is acceptable. So, in this case it is better to use non-throwing `tag_invoke` overloads. In addition, for customising conversion of composite types, always use `tag_invoke` overload with 2 context parameters. This will allow correct context propagation to elements of composites. This will also allow propagation of exceptions from conversion of elements.
156/4350 · 435
5
:46
English
Conversions for Third-Party Types
8/330 · 33
5
:32
English
It exposes both a sequence API and a tuple API. But converting from <<ref_value>> to `user_ns::ip_address` would not be able to use implementation for sequences, since those are constructed empty and then populated one element at a time, while `ip_address` has a fixed size of 4. The tuple conversion would fit, though. The only problem is that <<ref_is_tuple_like>> has a lower priority than <<ref_is_sequence_like>>. In order to circumvent this, the user only needs to specialize <<ref_is_sequence_like>> to not match `ip_address`.
377/5330 · 533
5
:37
English
If you need to combine incremental parsing with direct parsing, you can resort to <<ref_parser_for>>. `parser_for<T>` is an instantiation of <<ref_basic_parser>> that parses into an object of type `T`, and is what <<ref_parse_into>> uses under the hood.
210/2530 · 253
5
:24
English
The order of insertions is preserved, as long as there are no removals.
19/710 · 71
5
:30
English
For the class `ip_address` from the section <<custom_conversions>> this overload may look like this:
84/1000 · 100
5
:38
English
Forward declarations of contextual conversions are done very similarly:
21/710 · 71
5
:28
English
``` void tag_invoke( const value_from_tag&, value& jv, ip_address const& addr ) { jv = array{ b[0], b[1], b[2], b[3] }; } ```
137/1250 · 125
5
:27
English
**number**: An integral or floating point value.
15/480 · 48
5
:43
English
Similar to its standard library counterpart, elements may be accessed directly by their 0-based index with bounds checking using <<ref_array_at>>, or without bounds checking using <<ref_array_operator_lb_rb>>:
166/2090 · 209
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
5
:21
English
require that <<ref_value>> be declared as a class template, which would impose an additional compilation burden. By avoiding the template, most of the function definitions in the library can be excluded from the headers and emitted in a separate static or dynamic library.
101/2720 · 272
5
:36
English
CBOR
4/100 · 4
5
:27
English
include::quick_look.adoc[] include::dom/overview.adoc[] include::allocators/overview.adoc[] include::io/overview.adoc[] include::conversion/overview.adoc[] include::examples.adoc[] include::faq.adoc[] include::benchmarks.adoc[] include::comparison.adoc[] include::reference.adoc[] include::../../CHANGELOG.adoc[]
312/3120 · 312