Daniel Alley

I've found using serde very troublesome for serialization. XML just doesn't fit into the serde model very well The manual (non-serde) way to do this would be: ```rust // writer.write_event(Event::Decl(BytesDecl::new(b"1.0",...

Suggestions : * Move this functionality directly to `Attribute` * Provide a fast path to get the raw value TODO: * Character reference & entity reference substitution with associated error...

I plan to continue working on this over the next week or two

@Mingun Questions: Currently we have the functions `unescaped_value`, `unescaped_value_with_custom_entities` and their `decode` equivalents, that do the escaping part but don't implement the rest of the XML attribute-value-normalization spec. I'm not...

I'm basically going off of the lack of any kind of discussion of attribute value normalization in the HTML living spec, and this discussion on stackoverflow https://html.spec.whatwg.org/multipage/dom.html#attributes https://html.spec.whatwg.org/multipage/syntax.html#attributes-2 https://stackoverflow.com/questions/63906320/html5-attribute-value-normalization >...

This is currently possible to do with the raw, non-serde API. ```Rust use quick_xml::{Writer, events::Event, events::BytesDecl, events::BytesText, events::BytesStart, escape::partial_escape}; use std::fs::File; use std::io::Cursor; use std::io::Write; fn main() -> Result {...

Also this issue seems like a duplicate of https://github.com/tafia/quick-xml/issues/350

Thanks, that is helpful! What about quick-xml without a state machine, just nested readers? I've seen a couple of projects doing it, and it's the way my code is written...

Also a comparison against DHAT / Massif (from Valgrind) and perhaps DHAT (the Rust library, which is different from the Valgrind one) would be useful. This tool looks great but...

> Maybe in some future you are planning to change the code so that it dumps profiling data to disk in chunks in order to not store everything in memory...