hifijson VS roxmltree

I have recently encountered similar problems as you and also created a JSON crate, hifijson. Its unique idea is that JSON parsing itself is not so hard, but JSON lexing is! Therefore, my crate provides a JSON lexer that you can use to create your custom JSON parser with any functionality you need. For example, this allows you to ignore escape sequences, giving you a &str for strings. Or, if you care about escape sequences, hifijson gives you a Cow similarly to serde_json, allocating new memory only if necessary.

This is exactly what I needed when implementing xml-mut :D I have used roxmltree instead and manipulated text directly. will try to rewrite it using Xot.

In regards to the benchmarks, It makes sense to measure serializing/deserializing for parser crates. but since we are talking about dom implementations, metrics like traversal/iteration speed or insert/modification performance would be useful. a good example is roxmltree crate (readonly xml dom) which benches traversal/iteration performance and shows that by only focusing on readonly usecases, it gains substantial performance gains.

For xml parsing, I find https://github.com/RazrFalcon/roxmltree as a really good crate. It’s fast, light, and well documented/maintained. I have so much respect for the maintainer’s approach to merging PRs and the way they consider what’s important for the crate

I understand. But I've also wrote enough parsers and performance sensitive code in Rust (ttf-parser, tiny-skia, roxmltree). And in my experience, unsafe is not needed in 99% of the cases. Even something as performance sensitive as tiny-skia is unsafe-free (with some nuances).