What is the reasoning behind using Rust?

Open
#1 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
robotics

Research direction

No files, tests, or implementation entry points are identified. Read the repository description and the linked Support Guidelines, then use the Discussions page for this design question; it is done when the project’s rationale for Rust and its intended standalone use are documented or answered there.

Written by the indexing model from the issue text.

Description

I am curious as to what is the reason behind using rust for the multi agent path planning framework? I am very new to rust and this is rather interesting. Is it going to be a standalone application to develop path planners?

Dominant language
Rust
Stars
82
Forks
15
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-rmf/mapf

All issues in open-rmf/mapf

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.