method signatures
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading the encode(), decode(), and corresponding _with_offset() routines, then inspect how their usize results behave with undersized source or destination buffers. Compare the cited desert implementation and determine the intended API and error semantics; done means the signatures and offset routines have a clearly agreed replacement, with tests covering buffer-too-small failures.
Written by the indexing model from the issue text.
Description
encode() and decode() both have failure modes if you pass in a source or destination buffer that is too small but the return type is usize for both encode() and decode().
The _with_offset() routines could likewise be removed, since slices in rust are very cheap.
These are the routines I'm using inline in desert but I considered using this varinteger first:
- Dominant language
- Rust
- Stars
- 15
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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 datrs/varinteger
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
datrs/varinteger#8 ·
All issues in datrs/varinteger
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
bug rules
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
IronCoreLabs/ironcore-alloy#346 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100