Mismatching types between divviup-client and libprio-rs/janus
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 66
Description
In divviup-client, we have types that don't cleanly match those of the janus and libprio-rs crates.
For instance, in Vdaf we have length and bits parameters that need to be converted to usize for use in libprio-rs. Ideally the divviup-client representations would match those of janus and libprio-rs, so the user doesn't need to handle .into()/.try_into()/as conversions.
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.
Research direction
Start by reviewing cli/src/tasks.rs and comparing its Vdaf representations with the corresponding types in divviup-client, janus, and libprio-rs. Identify the mismatched parameters such as length and bits, then confirm the work is complete when callers no longer need the described into(), try_into(), or as conversions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100