bug fix: In bruteforce.h, searchKnn return less element than expected when using filter.
          #597
        
          
      
  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.
  
    
  
    
Bug Description
This bug will occur when less than
kelements are added intotopResults, and the remaining elements all failed to satisfydist <= topResults.top().first(Notice thattopResults.size() < know).If there sure is
kelements satisfydist <= topResults.top().first, the function should return them regardless of their internal order.Example
When calling
searchKnnwith filter, the following code may cannot fill thetopResultsto sizek.If the above loop only fill one nearest element into
topResults, the following loop will never satisfydist <= lastdist, aslastdistis the nearest element. Under this circumstance, the function will only return 1 element regardless ofk.