this post was submitted on 30 Sep 2025

35 points (100.0% liked)

Rust

7466 readers

20 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

EdTheLegendary@programming.dev

kahnclusions@programming.dev

torcherist@programming.dev

35

Godot-Rust: September 2025 dev update (godot-rust.github.io)

submitted 1 month ago by turbohz@programming.dev to c/rust@programming.dev

4 comments fedilink hide all child comments

cross-posted from: https://programming.dev/post/38340328

you are viewing a single comment's thread
view the rest of the comments

[–] thingsiplay@beehaw.org 3 points 1 month ago (1 children)

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?

[–] TitanNano@vger.social 1 points 1 month ago

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.