Re:Ask HN: What happened to flatbuffers? Are they being used?
by anonymoushn on Tuesday January 17, 2023 @06:04PM
(#34420788)
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.
Re:Ask HN: What happened to flatbuffers? Are they being used?
by secondcoming on Tuesday January 17, 2023 @07:17PM
(#34421479)
yes, rapidjson also supports optional insitu parsing.
Re:Ask HN: What happened to flatbuffers? Are they being used?
by tylerhou on Tuesday January 17, 2023 @09:36PM
(#34422767)
Copying into a string is a safe default. Also, proto’s API currently returns string references (and not views) so making a copy is required for open source.
(Although now std::string_view is common, I hear rumors that the proto API might change…)
Re:Ask HN: What happened to flatbuffers? Are they being used?
by secondcoming on Wednesday January 18, 2023 @05:45AM
(#34425302)
I don't think it was about safety. It was because they didn't want to make ABSL part of the public API.
It does not support std::string_view (or any equivalent). Google's internal protobuf does support ABSL's string view though, but it's not public.