Rebase with upstream v2.10.0 #36
Open
Conversation
This file contains 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
Fix: undefined var error in `remove` api
* Add threads linker option on linux Latest versions of libc (>= 2.34, released on August, 2021) have libpthread built in but in slightly older libcs one has to still specify -llibpthread to explicitly link it in The commit makes sure usearch compiles successfully with these older libcs * Use is_dummy() instead of repeating dummy predicate check logic
## [2.8.15](unum-cloud/usearch@v2.8.14...v2.8.15) (2024-01-09) ### Fix * exporting quantization enums in Go (unum-cloud#336) ([93c74c3](unum-cloud@93c74c3)), closes [unum-cloud#336](unum-cloud#336)
* Add move construction tests and fix an issue caused by them * Only consider zero length IO an error if input buffer was larger than zero * Move option-override policy opt-in before policy definitions so overrides actually take effect
Related to unum-cloud#320
## [2.8.16](unum-cloud/usearch@v2.8.15...v2.8.16) (2024-01-24) ### Docs * Downloads numbers ([13cc624](unum-cloud@13cc624)) ### Fix * SimSIMD dispatch ([c8dc3b7](unum-cloud@c8dc3b7)), closes [unum-cloud#320](unum-cloud#320) ### Make * Fix Node version for SemVer ([a68fca6](unum-cloud@a68fca6)) * Upgrade dependencies ([6ab2150](unum-cloud@6ab2150)) * Upgrade Node environment ([f5b6750](unum-cloud@f5b6750))
Fix invalid automatically being assigned on bug report creation
…ernal and internal storage
…o avoid issues when size_t is small
Per C00 and C++ standards[1], undefined macros are replaced with zero
Since stdint header is not included when using pointer sizes to determine cpu word size,
USEARCH_64BIT_ENV is always defined
The commit brings in cstdint header to make sure the appropriate arch header is defined
[1]: https://stackoverflow.com/questions/5085392/what-is-the-value-of-an-undefined-constant-used-in-if
In the past, if we got "too lucky" traversing the graph, we could exit early before accumulating K top matches, even if the index had more than K entries. This patch changes that behavior, making output more predicatable.
…ct on regression tests
…ng distance under the hood
Previously we were downcasting floats to the target type (e.g. int8_t), and then clamping to [-100, 100] range. This means that e.g. 129 would be cast to -127 and then converted to -100, in stead of becoming 100 The fix does clamping first, and then casts the resulting number (which is guaranteed to be in range [-100, 100], due to clamping) from source type to target int8_t. Given the clamping, this will never overflow.
When converting floating point arrays to binary, we use bitwise OR operations to set the relevant bits in the output buffer to 1. We do nothing if the bit is zero, so we assume that the bit is zero to start with. The memset statement makes sure this assumption holds.
…ix typo in tests and benchmark
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.
No description provided.