rapidjson
Rapidjson is an attempt to create the fastest JSON parser and generator. - Small but complete. Supports both SAX and DOM style API. SAX parser only a few hundred lines of code. - Fast. In the order of magnitude of strlen(). Optionally supports SSE2/SSE4.2 for acceleration. - Self-contained. Minimal dependency on standard libraries. No BOOST, not even STL. - Compact. Each JSON value is 16 or 20 bytes for 32 or 64-bit machines respectively (excluding text string storage). With the custom memory allocator, parser allocates memory compactly during parsing. - Full RFC4627 compliance. Supports UTF-8, UTF-16 and UTF-32. - Support both in-situ parsing (directly decode strings into the source JSON text) and non-destructive parsing (decode strings into new buffers). - Parse number to int/unsigned/int64_t/uint64_t/double depending on input - Support custom memory allocation. Also, the default memory pool allocator can also be supplied with a user buffer (such as a buffer allocated on user's heap or - programme stack) to minimize allocation. As the name implies, rapidjson is inspired by rapidxml.
Install
dotnet add package rapidjson --version 0.11.0
Install-Package rapidjson -Version 0.11.0
<PackageReference Include="rapidjson" Version="0.11.0" />
Frameworks
No framework metadata available.
Dependencies
No declared dependencies.
Adoption guide
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.