feat(frecency): use blake3 hash as db key for accesses #1908
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.
We replace the raw struct key with a hash to ensure database keys are fixed-size and uniform, which improves storage efficiency and lookup performance. This also avoids issues with variable-length or complex struct keys, and makes the database more robust against future changes to the key's serialization format.
Closes #1905
Closes #1895
Closes #1832
Closes #1727
Steps
fuzzy/init.lua
LMDB has a limit 511 bytes for key size, and will throw exception if larger than that, which is the case of CompletionItemKey with the combination of AI Code companion like Github Copilot.