You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The responses from Search are not guaranteed to be sorted by distance. I figure that overhead is best left to the caller as the library intends on being a low-level implementation.
Also, the results are not guaranteed to the closest N matches—the structure makes some accuracy tradeoffs in the interest of performance. I have not looked at the code in a while and there may be an elegant way to improve the guarantees. It's not top of mind for me but I welcome any contributions.
Hey Team,
Is the following test case correct?
I think 66 is closer to 64.5 as compared to 62. Or am I missing something here?
The text was updated successfully, but these errors were encountered: