3 ms·
Really interesting that nlohmann isn't fully compliant. What cases are these? It seems to me though that if you're encountering the edges of json where nlohman
by henshao 2y ago
Really interesting that nlohmann isn't fully compliant. What cases are these?
It seems to me though that if you're encountering the edges of json where nlohmann or simple parsing doesn't work properly, a binary format might be better. And if you're trying to serialize so much data that speed actually becomes an issue, then again, binary format might be what you really want.
The killer feature of nlohmann are the the NLOHMANN_DEFINE_TYPE_INTRUSIVE or NLOHMANN_DEFINE_TYPE_NON_INTRUSIVE macros that handle all of the ??? -> json -> ??? steps for you. That alone make it my default go to unless the above reasons force me to go another direction.
- nlohmann 2y agoIs there an example where nlohmann/json is not compliant? Would like to know (and fix) this.