Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Writting a RUST wrapper for MoveIt2 #2996

Open
Akumar201 opened this issue Sep 11, 2024 · 1 comment
Open

Writting a RUST wrapper for MoveIt2 #2996

Akumar201 opened this issue Sep 11, 2024 · 1 comment
Labels
enhancement New feature or request stale Inactive issues and PRs are marked as stale and may be closed automatically.

Comments

@Akumar201
Copy link

Is your feature request related to a problem? Please describe.

As Rust continues to grow in popularity, especially in systems programming and robotics, it would be great to have a Rust wrapper for MoveIt. Currently, integrating MoveIt into Rust-based projects is difficult, and a wrapper would simplify this process and allow seamless integration with Rust projects.

Describe the solution you'd like

I propose writing a Rust wrapper for MoveIt that exposes its core functionalities in a way that is idiomatic to Rust. This would allow Rust developers to easily integrate MoveIt into their projects while leveraging Rust's safety and concurrency features.

Describe alternatives you've considered

  • Manually integrating MoveIt with Rust using FFI (Foreign Function Interface), but this can be cumbersome and error-prone.
  • Relying on C++ as the primary language, but this makes it difficult for Rust projects to use MoveIt natively.

Additional context

This wrapper could serve as a bridge between MoveIt and the growing Rust ecosystem, allowing for safer and more efficient integration of robotics functionalities into Rust-based projects.

I am looking for collaboration with the people who are interested in this.

@Akumar201 Akumar201 added the enhancement New feature or request label Sep 11, 2024
Copy link

This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.

@github-actions github-actions bot added the stale Inactive issues and PRs are marked as stale and may be closed automatically. label Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale Inactive issues and PRs are marked as stale and may be closed automatically.
Projects
None yet
Development

No branches or pull requests

1 participant