VinÃcius dos Santos Oliveira wrote:
You're missing the point. I don't want the DOM intermediate representation. It's not needed.
I get that. I also get the appeal and the utility of pull parsers. But my point is that I can make that work today, quite easily, using Boost.JSON. It's 2020. Boost has zero pull JSON parsers. (I counted them, twice.) The "boost" implementation on https://github.com/kostya/benchmarks#json uses PropertyTree and is leading from behind. Maybe Boost.JSON can be refactored and a pull parser can be inserted at the lowest level. But in the meantime, there are people who have actual need for a nlohmann/json (because of speed) or RapidJSON (because of interface) replacement, and we don't have it. It doesn't make much sense to me to wait until 2032 to have that in Boost.