Amael
Amael
Indeed it seems a prettier way Is this way good for you ? ``` use std::any::Any; trait Register: Any { fn id(&self) -> i32; } #[macro_export] macro_rules! register_impl { ($name:ident)...
Yes exactly, the enum this is probably the better way But this implied to add all register under an enum and pass the register through the enum every time. Which...
Concerning the any trait I put it in order to downcast the ref for specific cp reg which required struct to be read / write But yes this is not...
Read them in specific functions imply that read_batch functionality is lost for such Register?
Another question, about the dev branch, the instruction hook why to make them different from x86 and arm64 for example? Couldn't it be harmonised under a common Type (Like for...