On Mon, Sep 23, 2019 at 5:19 AM Dominique Devienne via Boost
Hi,
What about performance? Have you heard of https://github.com/lemire/simdjson? Where would your library fall in that benchmark at the above link? Finally, there are many corner cases in JSON parsing. Is there the equivalent of Autobabhn for WebSocket, but for JSON parsing? Any plans to integrate with such infrastructure, assuming there's one?
There's also https://github.com/miloyip/nativejson-benchmark which benchmarks both performance and conformance.
The already mentioned and popular nlohmann/json has a convenient API, but fairs poorly in that benchmark for example.
Also, in client/server communications, it's less often a few huge JSON documents, but rather lots of small documents, so the constant "startup" time of the parser matters too, and in that same vein, a PULL-parser that allows to build the native data-structures directly, rather than the DOM-like approach of fully converting the document to a built-in JSON object, and then convert that to the native-structure, avoids the temp document, which is especially useful for large documents.
It looks like nlohmann/json now has this kind of API too: 1. https://tinyurl.com/nl-json-parse 2. https://tinyurl.com/nl-json-parse-callback Glen