Open
Conversation
This now passes faiss old tests, but doesn't really exercise any of the new XBufVector functionality yet.
Closed
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
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.
From @steveyen -->
This now passes faiss old tests, but doesn't really exercise any of the new XBufVector functionality yet.
This PR seems to compile, but it does not pass tests -- especially, the ONDISK.test_add fails because I think it's not using an BufIOReader.
Latest news on this... the old tests now pass. But, that doesn't mean the new codepaths are getting invoked and exercised.
It shows a couple examples of replacing std::vector with XBufVector -- and with replacing calls to READVECTOR() with X_READVECTOR().
"the old tests now pass" ==> correction on this ==> I meant to say the old tests now pass no worse or better than before! On my dev computer, the old tests didn't fully 100% pass before I started working on this... especially, on the ThreadedIndex tests...