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
When reworking the examples so they can be run as part of the doc tests, I came across the EnumAccessor alias feature, which was advertised to prevent name clashes.
Here's how I envisioned it:
error: Duplicate accessor a
--> src/lib.rs:192:12
|
9 | #[accessor(a as a_big: u32, except(Variant1,Variant2))]
| ^^^^^^^^^^
I realise this feature is meant to prevent name clashes with existing methods rather than other enum variant members, but I think this usecase is intuitive and can be surprising when it breaks this way.
I want to get feedback on whether this a feature we want to support or not.
The text was updated successfully, but these errors were encountered:
When reworking the examples so they can be run as part of the doc tests, I came across the
EnumAccessor
alias feature, which was advertised to prevent name clashes.Here's how I envisioned it:
But it errors:
I realise this feature is meant to prevent name clashes with existing methods rather than other enum variant members, but I think this usecase is intuitive and can be surprising when it breaks this way.
I want to get feedback on whether this a feature we want to support or not.
The text was updated successfully, but these errors were encountered: