Trying to understand why this does what it does.

Hi, I saw your post on rust discourse, and ended up here. I have been looking at enum_dispatch and similar projects.

I am trying to understand if this does something different, than another approach I was thinking of using in my project.


// from readme 

#[derive(EnumDowncast)]
enum Enum {
    Player(Player),
    Enemy(Enemy),
    Items { vec: Vec<Item> },
    #[enum_downcast(skip)]
    Other,
}

let container = Enum::Player(Player { name: "Ryo".to_string() });
let _player_ref: &Player = container.downcast_ref::<Player>().unwrap();
let _player_mut: &mut Player = container.downcast_mut::<Player>().unwrap();
let player: Player = container.downcast::<Player>().unwrap();

I was considering using macro to automatically implement TryFrom<_> trait

impl TryFrom<Player> for Enum {
...
}

impl TryFrom<Enemy> for Item {
...
}

// ..and so on

So you can do

let container = Enum::Player(Player { name: "Ryo".to_string() });
let player: Player = container.try_into().unwrap();

Does downcast solve a similar problem, or is it doing something else?

Also, this would be good for the readme: how does downcast handle the Items variant? That seems like an interesting case. :)

ryo33 / enum_downcast

Trying to understand why this does what it does. #1