You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thing that has come up in some of my work is that the rename options do not have a way to automatically include e.g. the full module path. Example:
struct A;
mod B {
struct A;
}
In this example the struct name for both B::A and A would be the same, unless it's somehow overriden. This becomes more of an issue when working with structs from e.g. different crates.
I'd prefer not to build something dedicated to this into this crate, but either of the issues you linked is still a possibility so I'll close in favor of those.
I think where this is unique is in applying the rename to the base struct name, rather than a field-level rename (which doesn't work nicely for things like Vec).
One thing that has come up in some of my work is that the rename options do not have a way to automatically include e.g. the full module path. Example:
In this example the struct name for both B::A and A would be the same, unless it's somehow overriden. This becomes more of an issue when working with structs from e.g. different crates.
This is related to previously discussed issues:
but much more specific since it's just a case of needing crate/module unique identifiers.
The text was updated successfully, but these errors were encountered: