Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

StringZilla 4.0! #201

Open
wants to merge 75 commits into
base: main
Choose a base branch
from
Open

StringZilla 4.0! #201

wants to merge 75 commits into from

Conversation

ashvardanian
Copy link
Owner

@ashvardanian ashvardanian commented Dec 7, 2024

This PR entirely refactors the codebase and separates the single-header implementation into separate headers. Moreover, it brings faster kernels for:

  • Levenshtein edit distances for DNA alignment and UTF-8 fuzzy matching,
  • Needleman-Wunsch pairwise global alignment for proteins,
  • AES-based hashing functions,
  • Multi-pattern search,

And more community contributions:

Why Split the Files? Matching SimSIMD Design

Sadly, most of the modern software development tooling stinks. VS Code is just as slow and unresponsive as the older Atom and the other web-based technologies, while LSP implementations for C++ are equally slow and completely mess up code highlighting for files over 5,000 Lines Of Code (LOCs). So, I've unbundled the single-header solution into multiple headers, similar to SimSIMD.

Also, similar to SimSIMD, CPU feature detection has been reworked to separate serial implementations, Haswell, Skylake, Ice Lake, NEON, and SVE.

Faster Sequence Alignment & Scoring

Faster Hashing Algorithms

Multi-Pattern Search

ashvardanian and others added 30 commits November 30, 2024 17:39
`sz_checksum`, `sz_hash`,
`sz_edit_distance_utf8`,
`sz_edit_distance_bounded`,
`sz_edit_distance_utf8_bounded`.
ashvardanian and others added 30 commits December 7, 2024 18:32
Imported from #169

Co-authored-by: ashbob999 <[email protected]>
Imported from #169

Co-authored-by: ashbob999 <[email protected]>
Co-authored-by: Alex Bondarev <[email protected]>
The new uniform behavior across the project
is to return a value different from `SZ_SIZE_MAX`
when the limit is reached, to differentiate memory
allocation and other errors.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants