NVIDIA / NVIDIA/cuvs

Make Base IVF List Interface Internal

Open
#1,726 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
Cuda
Stars
854
Forks
236
Avg merge
3d 3h
Merged PRs (30d)
62

Description

Users should never directly be mutating this object (list_base in common.hpp) and we might not have to be too vigilant with strict purely virtual interface semantics. We can make this class internal, so that only cuVS functions are capable of changing it.

Contributor guide

Open the contributing guide

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.

Research direction

Start with the list_base definition in common.hpp and trace the cuVS functions that access it. Review any existing tests for this interface; done means users cannot directly mutate the base IVF list while cuVS functions can still change it.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.