Represents an XML 1.0 document as a read-only tree.
Because in some cases all you need is to retrieve some data from an XML document. And for such cases, we can make a lot of optimizations.
As for roxmltree, it's fast not only because it's read-only, but also because it uses [xmlparser], which is many times faster than [xml-rs]. See the Performance section for details.
Sadly, XML can be parsed in many different ways. roxmltree tries to mimic the behavior of Python's lxml.
Unlike lxml, roxmltree does support comments outside the root element.
Fo more details see docs/parsing.md.
* Rust-based for now.
| Feature/Crate | roxmltree | [xmltree] | [elementtree] | [sxd-document] | [treexml] |
| ------------------------------- | :--------------: | :--------------: | :--------------: | :--------------: | :--------------: |
| Element namespace resolving | ✔ | ✔ | ✔ | ~1 | |
| Attribute namespace resolving | ✔ | | | ✔ | |
| [Entity references] | ✔ | ⚠ | ⚠ | ⚠ | ⚠ |
| [Character references] | ✔ | ✔ | ✔ | ✔ | ✔ |
| [Attribute-Value normalization] | ✔ | | | | |
| Comments | ✔ | | | ✔ | |
| Processing instructions | ✔ | ⚠ | | ✔ | |
| UTF-8 BOM | ✔ | ⚠ | ⚠ | ⚠ | ⚠ |
| Non UTF-8 input | | | | | |
| Complete DTD support | | | | | |
| Position preserving2 | ✔ | | | | |
| xml:space
| | | | | |
| Tree modifications | | ✔ | ✔ | ✔ | ✔ |
| Writing | | ✔ | ✔ | ✔ | ✔ |
| No unsafe | ✔ | ✔ | ~3 | | ✔ |
| Size overhead4 | ~62KiB | ~80KiB | ~96KiB | ~130KiB | ~110KiB |
| Dependencies | 1 | 2 | 18 | 2 | 14 |
| Tested version | 0.2.0 | 0.8.0 | 0.5.0 | 0.2.6 | 0.7.0 |
| License | MIT / Apache-2.0 | MIT | BSD-3-Clause | MIT | MIT |
Legend:
Notes:
string_cache
crate.```text test largeroxmltree ... bench: 8,859,229 ns/iter (+/- 17,173) test largesdxdocument ... bench: 10,092,993 ns/iter (+/- 224,417) test largexmltree ... bench: 32,025,637 ns/iter (+/- 49,911) test largetreexml ... bench: 32,577,612 ns/iter (+/- 88,429) test largeelementtree ... bench: 32,615,187 ns/iter (+/- 74,479)
test mediumroxmltree ... bench: 1,095,610 ns/iter (+/- 2,544) test mediumsdxdocument ... bench: 3,710,940 ns/iter (+/- 12,006) test mediumtreexml ... bench: 11,505,751 ns/iter (+/- 12,405) test mediumxmltree ... bench: 11,686,290 ns/iter (+/- 34,964) test mediumelementtree ... bench: 11,993,620 ns/iter (+/- 10,132) ```
roxmltree uses [xmlparser] internally, while sdx-document uses its own implementation and xmltree, elementtree and treexml use the [xml-rs] crate. Here is a comparison between xmlparser and xml-rs:
```text test largexmlparser ... bench: 2,050,485 ns/iter (+/- 1,105) test largexmlrs ... bench: 29,378,340 ns/iter (+/- 125,250)
test mediumxmlparser ... bench: 431,782 ns/iter (+/- 546) test mediumxmlrs ... bench: 10,612,855 ns/iter (+/- 9,050) ```
Note: tree crates may use different xml-rs crate versions.
You can try it yourself by running cargo bench
in the benches
dir.
unsafe
code.This library uses Rust's idiomatic API based on iterators. In case you are more familiar with browser/JS DOM APIs - you can check out tests/dom-api.rs to see how it can be converted into a Rust one.
Rust >= 1.18
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.