Question 1

How does json.cpp compare to nlohmann/json in speed and features?

Accepted Answer

json.cpp is 2-3x faster in parsing and compiles 10x faster, but it has a more minimal feature set and requires an external dependency, whereas nlohmann/json offers richer APIs and better integration with modern C++.

Question 2

How to set up json.cpp with CMake in my project?

Accepted Answer

You need to include json.h and json.cpp directly, and manually link against Google's double-conversion library, as the README doesn't provide CMake scripts, so setup may require additional configuration.

Question 3

Does json.cpp support JSON5 or non-standard extensions like comments?

Accepted Answer

It passes JSONTestSuite cases including comments, so it likely supports some extensions, but it's designed for strict conformance, so features like trailing commas or single quotes might not be supported.

Question 4

What C++ standard is required for json.cpp?

Accepted Answer

The library uses classic C++ and depends on standard libraries like and , so it should work with C++11 or later, but check the source for any specific compiler requirements.

Question 5

How to serialize float arrays without precision loss using json.cpp?

Accepted Answer

json.cpp remembers float types when assigned, so simply pass float values directly; it will serialize them efficiently using double-conversion, as demonstrated in the HTTP server example for embeddings.

Question 6

Is json.cpp thread-safe for concurrent parsing and serialization?

Accepted Answer

The README doesn't specify thread safety; given its minimal design, it's likely not inherently thread-safe, so you should synchronize access in multi-threaded environments to avoid issues.

json.cpp

What is json.cpp?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions