Migrate cuVS Integrations to the C API - #5627
Draft
tarang-jain wants to merge 3 commits into
Draft
tarang-jain wants to merge 3 commits into
tarang-jain wants to merge 3 commits into
Conversation
Target cuVS release/26.10 and retain documented C++ fallbacks for APIs not exposed through C.
Requires tarang-jain/cuvs faiss-c-api-extensions at a5b45b92.
Requires tarang-jain/cuvs faiss-c-api-extensions at f90a8d13.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
C API offers ABI stability guarantees, which should make this more robust to C++ breaking changes. Users can upgrade libcuvs underneath without affecting Faiss code. Some of the cuVS C APIs are still not up to date and need fallback on the C++ APIs.