Mingun
Mingun
I understand that, this is why I suggest to add a setting for those which does not have problems with they mouse.
This error produced because of `#[serde(deny_unknown_fields)]` on `Package`. When this option is enabled and flatten fields are present, then content firstly buffered in [`FlatMapDeserializer`](https://github.com/serde-rs/serde/blob/179954784683f35942ac2e1f076e0361b47f8178/serde/src/private/de.rs#L3184). Then internally tagged enum deserialized from...
> Some characters (like [control characters](https://github.com/tafia/quick-xml/issues/368), at least in XML 1.1), are legal when escaped but illegal otherwise, while others (like [NUL](https://stackoverflow.com/questions/730133/what-are-invalid-characters-in-xml)) are illegal in both cases. Yes, it is....
You are talking about #623, I meant [this](https://github.com/tafia/quick-xml/pull/496#issuecomment-1292669844) and [this](https://github.com/tafia/quick-xml/pull/496#issuecomment-1294142441) comments. With this change we can make life for some people easier untilw we implement proper solution that will check...
Honestly, it's not very clear why passing a reference makes you clone. Not vice versa? An example would be helpful.
In think, if do something like that, no need to introduce ambiguous syntaxes (for example, I read your definition as `(T = u32|u64), (U = bool || U = String)`)....
Quick question: does your fix prevents name clashing? So, for example, if you have two attributes `class` and `class_` in your KSY, how you will deal with that?
I would disagree with that. Why should a concrete translator implementation dictate rules for a language-agnostic language? Only the translator is responsible for ensuring that it does not create invalid...
Just let decision to concrete language generators. The reasonable default would be to add increasing number to the name to prevent conflict. If we have `class`, `class_` and `class1` fields,...
> @Mingun I'm not convinced that numeric suffixes are a good idea, Using numerical suffixes is not necessary, but it is the simplest scalable solution with clear semantics and predictable...