Exit Zen
6
:23
English
a series of member function calls to a user provided handler. This allows custom behaviors to be implemented for representing the document in memory.
38/1490 · 149
6
:76
English
While keys are strings, the mapped type of objects and the element type of arrays is the aforementioned type <<ref_value>> which can hold any JSON element, as seen in the previous assignments. Instead of building the JSON document using a series of function calls, we can build it in one statement using an initializer list:
135/3240 · 324
6
:26
English
which is optimized for parsing without subsequent modification. The <<ref_stream_parser>> object is reused between trials, allowing temporary memory allocated by the implementation to persist and improve performance.
109/2160 · 216
6
:50
English
This library adopts a "kitchen sink" approach. It contains a wealth of features, even those with niche uses. Its weakness is that the many template parameters, while allowing for configurability, inhibit the best possible optimizations. The consequence is that the library performs poorly. The ability to configure every aspect of the value type has the paradoxical effect of making it less suitable as a vocabulary type.
153/4210 · 421
6
:18
English
Serialize a <<ref_value>>, <<ref_array>>, <<ref_object>>, or <<ref_string>>
139/750 · 75
6
:52
English
To resolve the ambiguity manually, use an explicit constructor:
18/630 · 63
6
:36
English
`value_from` behavior
21/210 · 21
7
:9
English
Status]] |https://vinniefalco.visualstudio.com/json/_build/latest?definitionId=8&branchName=develop[image:https://img.shields.io/azure-devops/build/vinniefalco/2571d415-8cc8-4120-a762-c03a8eda0659/8/develop[Build Status]]
221/2210 · 221
7
:26
English
<<ref_object>>
33/140 · 14
7
:24
English
with a <<ref_string_view>>-based interface,
54/430 · 43
7
:76
English
More formally, if the number:
11/290 · 29
7
:54
English
As an example, let's implement conversion for https://en.cppreference.com/w/cpp/chrono/system_clock[``std::chrono::system_clock::time_point``s] using https://en.wikipedia.org/wiki/ISO_8601[ISO 8601] format.
164/2060 · 206
7
:46
English
The second, more powerful approach, is to provide the conversion implementation yourself. With Boost.JSON this is done by defining an overload of `tag_invoke` function (the benefits of this mechanism are outlined in http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1895r0.pdf[C++ proposal P1895]. In essence, `tag_invoke` provides a uniform interface for defining customization points by using argument-dependent lookup to find a viable overload from the point at which it is called. As the name suggests, a tag type is passed as an argument in order to:
232/5620 · 562
7
:27
English
itself.
6/100 · 7
7
:45
English
If <<ref_try_value_to>> is used with a type, for which there's no `tag_invoke` overload of the form described in this section, but there is one of the form intended for <<ref_value_to>>, then the library still tries to perform the conversion. It uses the throwing overload, and attempts to convert any thrown exception into an {ref_error_code}. Note, though, that such approach will likely be slower then a dedicated overload.
238/4260 · 426
7
:40
English
To avoid creating such temporaries with an incorrect {ref_memory_resource}, using <<ref_value>>'s member functions <<ref_value_emplace_array>>, <<ref_value_emplace_object>>, and <<ref_value_emplace_string>> can be helpful.
267/2220 · 222
7
:30
English
similar to {std_string}.
16/240 · 24
7
:55
English
Formatted Output
5/160 · 16
7
:25
English
{ref_polymorphic_allocator} do not acquire ownership; the caller is responsible for ensuring that the lifetime of the resource extends until it is no longer referenced.
70/1680 · 168
7
:34
English
The string provided by the
8/260 · 26