HData has introduced Data Request Management, a groundbreaking tool that streamlines the energy regulatory process by reducing manual workload and increasing efficiency.

HData has launched a comprehensive legislative data library, enabling energy sector professionals to easily track bills from Congress and all 50 states, enhancing regulatory insight.

Exclusive: The transaction aims to create the industry’s largest regulatory platform — and combat data fragmentation.

In today’s USEA Power Sector Podcast, Hudson Hollister, Founder and CEO of HData, an AI-native operating system for energy regulation, answered questions by jou...

I see. I was about to suggest macros as the only solution, and then I remembered that there are crates that provide these macros. In particular: https://docs.rs/derive_more/latest/derive_more/derive.From.html#example-usage This seems to work (it compiles): use derive_more::From; #[derive(From)] enum Aenum { B(Benum), C(Cdata), } #[derive(From)] enum Benum { F(Fdata), G(Gdata), H(Hdata), } struct Fdata { number: usize, char: char, payload: String, } struct Gdata { number: usize, } struct Hdata { number: usize, payload: String, } struct Cdata { payload: String, } let f = Fdata { number: 1, char: 'c', payload: "Hello!".to_string() }; let a_example = Aenum::from(Benum::from(f)); #[derive(From)] enum AenumRef<'a> { B(BenumRef<'a>), C(&'a Cdata), } #[derive(From)] enum BenumRef<'a> { F(&'a Fdata), G(&'a Gdata), H(&'a Hdata), } fn convert_r(f_ref: &Fdata) -> AenumRef<'_> { AenumRef::B(BenumRef::from(f_ref)) } with this dependency in `Cargo.toml` derive_more = { version = "2", features = ["from"] }

HData's acquisition of Insight Engine will revolutionize regulatory intelligence in the energy sector, streamlining analyses and enhancing data insights.