roxmltree VS strum

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

Take a look at the strum crate. https://crates.io/crates/strum

I would be use something like https://github.com/Peternator7/strum if I need map string to enum and serde is not the option.

Looks like proper support for this in strum has been proposed.

This crate can generate an iterator for you using a macro https://github.com/Peternator7/strum

The strum crate is also good for removing this kind of boilerplate, and worth checking out!

strum is among my favorite crates to recommend. Favorites of this crate include EnumProperty and EnumIter

I released my first crate that provides a derive macro to easily obtain a name of a current variant in an enum as a string. I did it mostly to learn about procedural macros and the process of releasing a crate. I then found out there is strum which does this and much more. Nonetheless, I learned a lot and I found couple of nice tools like ```cargo-release and git-cliff.

I used https://crates.io/crates/strum to iterate over the enum variants, otherwise you'd have to hardcode the list of variants and wouldn't gain anything.

If you chose to go with the "derive a trait" route the strum crate might be what you're looking for. It lets you use derive to add information about variant count, discriminants or even iterators over variants to an enum.

You might want something like strum