ROS 2 Rust Meeting: June 2025

ROS ROS General
, ,
1

The next ROS 2 Rust Meeting will be 2025-06-09T14:00:00Z

The meeting room will be at https://meet.google.com/rxr-pvcv-hmu

In the unlikely event that the room needs to change, we will update this thread with the new info!

1 Like
2

Hi,

Will the meetings be recorded or summary documented?
Would like to see what we are doing now and if there is anything interesting or can be helped with.
Regards.

3

I can try and give a summary of what we went over, sure! If I miss anything important (or misstate something), I’m sure @grey or @esteve can correct me.

Biggest takeaways:

  • Our code generator has been added to the buildfarm. This is an important first step in official adoption of the client library!
  • The Async Workers PR (Async Workers by mxgrey · Pull Request #446 · ros2-rust/ros2_rust · GitHub) has been merged. This is our way to try and make multithreading a bit easier to accomplish. Thank you @grey!
    • Future PRs are planned to hopefully streamline the general API of the client library a bit further so that it’s easier for people to use, but that may take a little while to complete.
    • In the meantime, if folks are interested in trying out the new Async Workers, please let us know how it goes! Feedback is welcome!
  • We also got a Windows Github action set up (Adding windows github action by knmcguire · Pull Request #485 · ros2-rust/ros2_rust · GitHub) so that we can keep an eye on how our windows builds are doing. We’ve noticed a slight bug with the builds, but that should hopefully be fixed in the near future. Thank you @KimMcG!
  • We are hoping to bundle things up into an official release very soon. There will be breaking API changes in this release, though. We apologize for that.
    • The future API changes that I mentioned earlier (the ones intended to streamline the API to improve ease-of-use) will also be a breaking change. But mostly because you won’t (usually) need to put .Unwrap() everywhere in your code. In theory. Again, we apologize, we don’t normally like to do two breaking changes in a row, but we felt it would be better to get the Async Workers out and in the hands of the community rather than wait an indeterminate amount of time for the other changes to be designed/refined/implemented/pushed.
  • Actions still need to be implemented - the Async Workers change means that we will need to re-think how we’re implementing these. But we have a couple members that have a few ideas about how to approach the problem.

And I think that’s everything? Please let me know if I’ve missed something! In the meantime, I hope the community likes the Workers paradigm - I personally think it’s a pretty neat solution to multithreading in ROS 2 Rust nodes, so I’m excited to see what the community creates with it!

3 Likes