How to set up ros2_rust on ROS 2 Humble?

Clone the required message packages and the rosidl_rust generator from the humble branches, then build with colcon. Source your ROS 2 installation and workspace, as detailed in the Humble section of the README, but be prepared for manual steps and potential workarounds.

Is rclrs ready for production use?

No, the library is still rapidly evolving with no stability guarantees, so it's best suited for development or experimental projects until it matures. Check the issue list for known limitations before committing.

ros2_rust vs C++ ROS 2: which should I choose?

Choose ros2_rust if you prioritize Rust's memory safety and modern async features for robotics, but opt for C++ with rclcpp if you need stable APIs, extensive documentation, and a mature ecosystem for production-critical systems.

How do I use async actions in rclrs?

rclrs supports async variants for action servers and clients; refer to the examples repository for implementation patterns, and use the executor or worker models to handle asynchronous callbacks safely.

What ROS 2 distributions does ros2_rust support?

It supports multiple distributions including Rolling, Kilted, Jazzy, and Humble, but each requires specific setup steps with temporary workarounds, such as cloning the rosidl_rust generator, as noted in the installation guide.

Can I use zero-copy messaging with rclrs?

Yes, loaned messages enable zero-copy messaging for performance optimization, but ensure your ROS 2 distribution and QoS settings are compatible, as detailed in the features section.

ros2_rust — ROS 2 Client Library for Rust

What is ros2_rust?

ROS 2 for Rust (ros2_rust) is a set of tools, including the rclrs client library and a code generator, that enables developers to write ROS 2 nodes and applications in the Rust programming language. It solves the problem of integrating Rust's safety and performance features into the ROS 2 robotics ecosystem, allowing developers to leverage ROS 2's extensive middleware while using Rust.

Target Audience

Robotics developers and engineers who are building ROS 2-based systems and want to utilize Rust's memory safety, concurrency features, and modern tooling. This includes teams working on performance-critical or safety-sensitive robotic applications.

Value Proposition

Developers choose ROS 2 for Rust because it provides a fully-featured, idiomatic Rust interface for ROS 2, prioritizing safety and performance while maintaining compatibility with the broader ROS ecosystem. It offers unique advantages like zero-copy messaging via loaned messages, async support for core communication patterns, and dynamic message handling, which are not as readily available in other ROS 2 language bindings.

Rust bindings for ROS 2

Use Cases

Best For

Building high-performance ROS 2 nodes where zero-copy messaging and low latency are critical.
Developing safety-critical robotic applications that benefit from Rust's memory safety guarantees.
Creating ROS 2 applications with complex async workflows, such as action servers and clients.
Integrating Rust's modern tooling and concurrency models into existing ROS 2 ecosystems.
Prototyping or building ROS 2 nodes that require dynamic message introspection and manipulation at runtime.
Teams transitioning from C++ to Rust for ROS 2 development who need a comprehensive and idiomatic Rust library.

Not Ideal For

Projects requiring long-term stability and API guarantees, as the library is still evolving with no stability promises.
Teams with tight deadlines or limited DevOps resources, due to the complex, distribution-specific installation process.
Applications dependent on ROS 2 features not yet implemented in rclrs, as indicated by the open issue list.

Pros & Cons

Pros

Comprehensive ROS 2 Support

Supports all core ROS 2 features including message generation for all types, publishers, subscriptions, services, actions, and async variants, as detailed in the features list.

Performance-Focused Design

Includes loaned messages for zero-copy messaging and tunable QoS settings, optimizing for low-latency communication critical in robotics.

Idiomatic Rust Integration

Provides modern Rust patterns like async support for actions and services, and worker/executor models for safe concurrency.

Dynamic Runtime Capabilities

Allows for dynamic message handling and introspection at runtime, enabling flexible and adaptive node behavior.

Cons

Unstable API

The README explicitly states no stability guarantees due to rapid evolution, making it risky for production systems without frequent updates.

Complex Setup and Dependencies

Installation requires different steps for each ROS distribution, manual cloning of repositories, and workarounds like installing extra packages (e.g., due to issue #557).

Limited Ecosystem Maturity

Compared to established bindings like rclcpp, the ecosystem is smaller, with missing features and ongoing development, as seen in the issue list.

What is ros2_rust?

Target Audience

Value Proposition

Use Cases

Best For

Building high-performance ROS 2 nodes where zero-copy messaging and low latency are critical.
Developing safety-critical robotic applications that benefit from Rust's memory safety guarantees.
Creating ROS 2 applications with complex async workflows, such as action servers and clients.
Integrating Rust's modern tooling and concurrency models into existing ROS 2 ecosystems.
Prototyping or building ROS 2 nodes that require dynamic message introspection and manipulation at runtime.
Teams transitioning from C++ to Rust for ROS 2 development who need a comprehensive and idiomatic Rust library.

Not Ideal For

Projects requiring long-term stability and API guarantees, as the library is still evolving with no stability promises.
Teams with tight deadlines or limited DevOps resources, due to the complex, distribution-specific installation process.
Applications dependent on ROS 2 features not yet implemented in rclrs, as indicated by the open issue list.

Pros & Cons

Pros

Comprehensive ROS 2 Support

Supports all core ROS 2 features including message generation for all types, publishers, subscriptions, services, actions, and async variants, as detailed in the features list.

Performance-Focused Design

Includes loaned messages for zero-copy messaging and tunable QoS settings, optimizing for low-latency communication critical in robotics.

Idiomatic Rust Integration

Provides modern Rust patterns like async support for actions and services, and worker/executor models for safe concurrency.

Dynamic Runtime Capabilities

Allows for dynamic message handling and introspection at runtime, enabling flexible and adaptive node behavior.

Cons

Unstable API

The README explicitly states no stability guarantees due to rapid evolution, making it risky for production systems without frequent updates.

Complex Setup and Dependencies

Installation requires different steps for each ROS distribution, manual cloning of repositories, and workarounds like installing extra packages (e.g., due to issue #557).

Limited Ecosystem Maturity

Compared to established bindings like rclcpp, the ecosystem is smaller, with missing features and ongoing development, as seen in the issue list.

ros2_rust

What is ros2_rust?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

ros2_rust

What is ros2_rust?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?