microsoft / microsoft/onnxruntime

Pushing Rust bindings forward

Open
#21,533 6 comments 6 reactions 0 assignees View on GitHub
feature request
Dominant language
C++
Stars
21.9k
Forks
4.2k
Avg merge
4d 11h
Merged PRs (30d)
184

Description

There has been a long discussion about adding Rust bindings to this repository( #11992 #7231), but I've noticed that there has been little progress on the Rust bindings since the initial PR #12606 . Here are some current to-do items that I think we can have some discussion around, and I'd be glad to make some contributions to push the Rust bindings forward.

- [ ] Verify the validity of existing rust bindings code: Because the Rust binding has not been maintained for quite some time and the Rust pipeline has been disabled(#19067 ), we need to verify the usability of existing code.
- [ ] Release a crate (From #18346)
- [ ] change name of the crates to be published (onnxuntime-rs and onnxruntime-sys are already taken and we'll need new names)
- [ ] update authors / license to reflect contributions from previous maintainer(s) and new maintainers
- [ ] introduce a crate publish GH action or ADO pipeline
- [ ] Necessary enhancement on current bindings such as #15655

Contributor guide

Open the contributing guide

Research direction

Review the existing Rust bindings and the disabled Rust pipeline referenced by #19067 first. Then inspect the crate-publishing requirements from #18346, including available crate names, contributor metadata, and a GitHub Actions or ADO pipeline. Done means the bindings are verified, a publishable crate has an agreed name and metadata, and publishing automation is in place; enhancements from #15655 also need consideration.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, rust
Domain
developer-experience, machine-learning, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.