Use a faster hash function
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- performance
Research direction
The issue names no files, tests, or entry points. Start by locating the current hash implementation in the repository and identify how its performance is measured; compare that path with rustc's FnvHasher and consider the work done when the faster hash function is used without breaking existing behavior.
Written by the indexing model from the issue text.
Description
e.g. rustc's FnvHasher
- Dominant language
- Rust
- Stars
- 212
- Forks
- 84
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 6
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from servo/string-cache
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
servo/string-cache#293 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
servo/string-cache#260 · 6 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
servo/string-cache#240 · 4 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
servo/string-cache#236 · 8 comments ·
All issues in servo/string-cache
Similar issues
-
bug CLI custom-model
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
rust-bitcoin/rust-bitcoin#6930 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fulcrumgenomics/ferro-hgvs#2251 ·
-
A-allocators A-docs C-enhancement T-libs
Difficulty 2/5 1-3 hours Newbie friendliness 75/100