rutenspitz VS roxmltree

Inline documentation is lacking, but the README and the examples show it off reasonably well.

Also! You might want to verify the correctness of your implementation against some reference implementation - e.g. indexmap, or just an inefficient but obviously correct HashMap + Vec combination. https://github.com/jakubadamw/rutenspitz makes this very easy, and it did discover a few logic bugs in tinyvec, so I recommend giving it a go!

https://github.com/jakubadamw/rutenspitz allows comparing your implementation against a slower, reference implementation using a fuzzer. Might be helpful for correctness, but is not really useful for testing concurrency, as far as I can tell.

There's also https://github.com/jakubadamw/rutenspitz that is already usable, but I'm not aware of it being widely deployed.

By the way, https://github.com/rust-fuzz/auto-fuzz-test and/or https://github.com/jakubadamw/rutenspitz will help mitigate that, if anyone is willing to apply them.

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).