Reverted (BREAKING)
- hash_hasher re-export in favor of using
git-hashtable.
Due to the importance of best-suited data structures for maximizing
performance we need to take control over them. This is best done using
a dedicated crate that can cater to our very needs. That very crate is
namedgit-hashtable.
Commit Statistics
- 10 commits contributed to the release over the course of 27 calendar days.
- 27 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
- Uncategorized
- prepare chnagelogs prior to git-repository release (7114bbb)
- Merge branch 'adjustments-for-cargo' (083909b)
- adjust to changes in
git-testtools(4eb842c) - Release git-hash v0.10.1, git-hashtable v0.1.0 (7717170)
- Merge branch 'main' into http-config (6b9632e)
- Merge branch 'optimize_hashtables' (95ad56c)
- hash_hasher re-export in favor of using
git-hashtable. (2761466) - use newly added git-hashtable (50cb436)
- switch to custom Hasher implementation (269d59e)
- Merge branch 'main' into http-config (bcd9654)