This errors are usually related to problems that are relted to data or conditions that happen only at run-time

Rational: since type erased numbers will always use at least 8 bytes it is faster to cast everything to either double, uint64_t or int64_t.

This errors are usually related to problems which "probably" require code refactoring to be fixed.

We're defining two standard layout types that have a char as a common initial sequence (as the Lambda is empty, it doesn't add anymore members to B).

@brief exception indicating access out of the defined range @sa https://json.nlohmann.me/api/basic_json/out_of_range/

@brief general exception of the @ref basic_json class @sa https://json.nlohmann.me/api/basic_json/exception/

A non-owning nullable reference to a socket. The reference is invalidated on socket close or destruction.

A non-owning nullable reference to a socket. The reference is invalidated on socket close or destruction.

DefaultAllocator uses new/delete to allocate memory regions

----------

A Unicode-aware identifier.

A token was consumed. Arguments: kind, begin, end

Allocator interface. This is flatbuffers-specific and meant only for `vector_downward` usage.

Result of parsing (wraps ParseErrorCode) ! \ingroup RAPIDJSON_ERRORS \code Document doc; ParseResult ok = doc.Parse("[42]");

! Input adapter for a (caching) istream. Ignores a UFT Byte Order Mark at beginning of input. Does not support changing the underlying std::streambuf

A tag to indicate an empty flatbuffers::optional<T>.

Class for preserving comments in xml see: https://stackoverflow.com/a/34324359/17094594

=== error handling ===//