ros2_rust
ros2_rust copied to clipboard
Rust bindings for ROS 2
A topic that emerged from the previous Rust WG meeting is the fact that rclrs currently lacks benchmarks for testing performance or efficiency of the client library. Adding such benchmarks...
Rather than merely a wrapper around the rcl c library and types, what other ways can we make the rclrs API more Idiomatic to rust design patterns and style? How...
It'd be nice to get some more feedback on the design/implementation of rclrs from the larger Rust community, e.g. are there better approaches to wrapping the rcl c library, code...
A big part in making Rust more attractive for ROS2 community and vice versa would be in providing released packages, making rclrs (or portions of) more readable installable. As may...
Given a topic type in the form of a string like "geometry_msgs/msg/Pose", this will * Parse the string into the package name "geometry_msgs" and the message name "Pose" (see the...
- Replace libc crate with `std::ffi` - Remove realloc and memcpy workaround https://github.com/ros2-rust/ros2_rust/issues/215#issuecomment-1279723455
**This is an overview PR to see the changes at a high level.** I recommend you check out this branch and run `cargo doc` to see what the API looks...
Currently, the implementation of `take_boxed()` will place the message on the stack during intermediate steps, even though the intent of this function is to avoid that, since large messages might...
We should apply the technique from https://github.com/ros2-rust/ros2_rust/pull/260 to client and service callbacks. Specifically, we could allow taking the request/response in a `Box`, and to optionally take a `ServiceInfo` argument (corresponding...
Currently, on each iteration of `rclrs::spin()`, the wait set is regenerated from scratch. It would be more efficient to be able to push new waitable entities, if any, into the...