Ttykuu

So I have an enum wrapping an enum, but I have another enum talking about what that enum is.

Which makes for a confusing English sentence, so here's an example.

I got one enum:

enum Example 
 A(Something),
 B structfield: K ,
 C(Gamma, Third),
 D(InsertSomethingElseCrazyHereThatCantImplementANYTraitsCauseReasons),

Which is all fine and dandy, but I needed another way to categorize them and compare the categories without matching. I also needed to pass along Examples without fields, and then I realized that I should probably use an enum describing my enum, so I ended up doing this:

#[derive(Eq, PartialEq, YouGetThePoint)]
enum ExampleCategory 
 A, B, C, D

Then, cause I wanna easily go from Example to ExampleCategory:

impl From<Example> for ExampleCategory 
 fn from(e: Example) 
 match e 
 Example::A(_) => ExampleCategory::A
 Example::B.. => ExampleCategory::B
 Example::C(_,_,_) => ExampleCategory::C,
 Example::D(_) => ExampleCategory::D
 
 

So now, every time I need to add an Example, I end up needing to change code in three different places, and if I want a new trait... etc. Also, if theSomethinginExample::A` were another kind of this enum. *shudders

I think I made my point on why this is probably a bad idea.

I'm 90% positive there's a better way to do this (that doesn't involve macros since I don't even know how I would go about doing that). How would I change this to be more DRY/better? Since the Example enum is actually a part of a larger issue.