Possible to catch conflicting renames?

[iamthad]

I recently found that I had made a typo and gave two different variants of an enum the same name using #[serde(rename=...)].

The code was something like,

#[derive(Deserialize, Serialize)]
pub enum Foo {
    #[serde(rename = "bar")]
    Bar { qux: int, },
    // oops! meant to type "baz"
    #[serde(rename = "bar")]
    Baz { qux: int, },
}

I was surprised that I didn't encounter any error when compiling, serializing, or deserializing.

A complicating factor is that (like in the example above) both variants have the same fields. Perhaps if this weren't the case, I would have encountered some errors while deserializing.

I can't think of any reason off-hand why it would be desirable to allow conflicting names. It seems like it would always cause loss of data.

Would it be possible to catch this type of conflict? Is there some reason I am not thinking of that allowing conflicting names is desired?

[Mingun]

Probably #2562 fixes that, but need to check. I got an impression that renames already was checked for uniquenesses.

[Mingun]

Although no, here it is assumed that all names are already unique, and if they are not, they silently collapse into one entry in the BTreeSet