Looking at the example code of Export Groups, I don’t understand why a #[export] is needed, if there is already a #[export_group(...)] or #[export_subgroup(...)] . Its surely possible in Rust to automatically invoke #[export] if one of the group-macros are invoked, right?
In the initial implementation, export groups have been added as an independent attribute. One attribute creates groups, and the other marks fields for exporting. So yes, this is not being auto-inferred right now, but it could probably be added.
In the initial implementation, export groups have been added as an independent attribute. One attribute creates groups, and the other marks fields for exporting. So yes, this is not being auto-inferred right now, but it could probably be added.
Looking at the example code of Export Groups, I don’t understand why a
#[export]is needed, if there is already a#[export_group(...)]or#[export_subgroup(...)]. Its surely possible in Rust to automatically invoke#[export]if one of the group-macros are invoked, right?In the initial implementation, export groups have been added as an independent attribute. One attribute creates groups, and the other marks fields for exporting. So yes, this is not being auto-inferred right now, but it could probably be added.
In the initial implementation, export groups have been added as an independent attribute. One attribute creates groups, and the other marks fields for exporting. So yes, this is not being auto-inferred right now, but it could probably be added.