Hacker News new | past | comments | ask | show | jobs | submit login

simdjson also does this sort of thing. All strings are decoded and copied to an auxiliary buffer. For strings without escape sequences in them or for end users who don't mind destroying the json document by decoding the strings in-place, these copies could be avoided. I may get around to shipping a version of simdjzon (the Zig port) that optionally avoids these copies (this sort of has to be optional because the current API lets you throw away your input buffer after parsing, and this option would mean you cannot do that), but porting this stuff back to C++ and getting it upstreamed sounds more difficult.



yes, rapidjson also supports optional insitu parsing.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: