Working on a lib for avoiding repetetive code when declaring components and macro calls, atm it generate use and derive globally and locally, soon custom derives for single components and auto deref for single type structs and more.
This seems quite interesting. But I still have some doubts about an use case. I think a Rust Proc macro that generates rust code from rust like code is a better approach since we get ide error check...
Do you plan on adding other ECS impls than Bevy because this could be a nice way of creating framework agnostic ecs definitions.