1

:11

= Frequently Asked Questions

28/10000 · 28

2

:13

English

These libraries are not comparable. The output of

49/10000 · 49

3

:14

English

the simdjson parser is a read-only structure. In other words, it can't be changed, and the only way to create one is by parsing a JSON string. On the other hand, Boost.JSON allows you to modify the container holding the parsed JSON, or even build a JSON document from scratch through the container interface.

308/10000 · 308

4

:20

English

Using standard allocators would

31/10000 · 31

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.

272/10000 · 272

6

:26

English

"Why use <<ref_storage_ptr>> over {ref_polymorphic_allocator}?:: {ref_polymorphic_allocator} treats the memory resource as a reference with respect to ownership. Boost.JSON uses a reference counted smart pointer container to simplify the lifetime management of memory resources. In addition to being reference counted, <<ref_storage_ptr>> can function as an uncounted reference wrapper around a {ref_memory_resource}.

417/10000 · 417

7

:34

English

The string provided by the

26/10000 · 26

8

:35

English

library uses the <<ref_storage_ptr>> allocator model, has the same interface on all C++ versions, and has an optimized class layout to keep the size of JSON values small. <<ref_string>> also implements an improved interface that replaces extraneous overloads with ones that use <<ref_string_view>>.

298/10000 · 298

The translation has come to an end.