Skip to content

[ENH] add Rust bindings #30

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

Merged
merged 5 commits into from
Feb 18, 2025
Merged

[ENH] add Rust bindings #30

merged 5 commits into from
Feb 18, 2025

Conversation

codetheweb
Copy link

@codetheweb codetheweb commented Feb 13, 2025

Moves Rust binding layer into this repo from https://github.com/chroma-core/chroma.

Decided to move the bindings here rather than moving the contents of this repo into chroma-core/chroma as going in the other direction muddies the CI in chroma-core/chroma. This also allows us to easily continue publishing the Python bindings.

This crate will be consumed via a git dependency. I do not plan on publishing it to crates.io in the near future.

@codetheweb codetheweb marked this pull request as ready for review February 13, 2025 01:51
@codetheweb codetheweb requested a review from HammadB February 13, 2025 02:06
@codetheweb codetheweb merged commit 57c14ff into master Feb 18, 2025
10 checks passed
@codetheweb codetheweb deleted the feat-rust-bindings branch February 18, 2025 19:12
codetheweb added a commit to chroma-core/chroma that referenced this pull request Feb 18, 2025
## Description of changes

Requires chroma-core/hnswlib#30 (CI will not
pass until that PR is merged).

Moves bindings to our fork of hnswlib. This means that the hnswlib repo
will no longer need to be a sibling of this repo for it to build
correctly.

## Test plan
*How are these changes tested?*

- [x] Tests pass locally with `pytest` for python, `yarn test` for js,
`cargo test` for rust

Moved Rust tests for bindings to hnswlib repo.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants