paritytech / paritytech/parity-common
consider replacing `uint` with `ruint`
Open
Nobody has claimed this yet.
F6-refactor
Q5-substantial
- Dominant language
- Rust
- Stars
- 311
- Forks
- 245
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/recmo/uint is a modern re-implementation of uint using const generics.
It doesn't suffer from issues like #388.
Would be nice to compare the numbers on our benchmarks between uint and ruint before making the move.
cc @kpp
Contributor guide
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.
Research direction
No files or tests are named. Start by reviewing the existing uint usage and benchmark entry points, then read the linked ruint implementation and investigate issue #388. Done means comparable benchmark results are available to support the replacement decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100