It could easily be the case that its just outside of the goals or scope of docx-rs, but I wonder. It would probably be pretty reasonable to add some kind of a c

It could easily be the case that its just outside of the goals or scope of docx-rs, but I wonder. It would probably be pretty reasonable to add some kind of a catch-all "unknown" variant, that backs itself up with storing the names of tags as interned strings? Justified under the idea that unexpected tags should be uncommon by the fact they are unexpected (if its common you should have expected it), and can be relegated to a less-performant cold-path as a result. It would probably mean not having the most fun time ever for the developer depending on docx-rs if an explicit requirement is interacting with and modifying a tag that ends up in the "whatever" bucket, but at least you could make sure that you (de)serialize losslessly.