`read_event` vs. `read_namespaced_event`

[pfernie]

Interleaving calls to read_event and read_namespaced_event could lead to surprising behavior (internal stack of namespaces would not be properly maintained?). It seems the Reader should always be either tracking or not tracking the namespaces, and as such should expose some configuration fn parse_namespaces(self, parse: bool) -> Self. That, or perhaps there should be separate implementations, EventReader, NamespacedEventReader, with only the latter exposing fns such as read_namespaced_event.

[pfernie]

I added a gist showing an (admittedly pathological) usage of read_event & read_namespaced_event to illustrate.

[Mingun]

Yes, the current design of reading namespaces are not good. I'd prefer that namespace buffer would be in the Reader, because, unlike buffer for events, I cannot imagine why the user may want to clear it -- if he/she would do that, he/she lose all namespaces information and probably even breaks quick-xml.

PR for moving namespaces buffer inside Reader and always be aware of namespaces is welcome.

[dralley]

@Mingun Is there any work left here or can it be closed?

[Mingun]

Done in #437, can be closed