Implement range indexing
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start by locating the NonEmpty indexing implementation and its existing usize behavior, then compare it with Rust's Range, RangeFrom, RangeTo, and RangeFull indexing on Vec. Add coverage for the four range forms shown in the issue and verify that each expression compiles and returns the expected slice.
Written by the indexing model from the issue text.
Description
It should be possible to index a NonEmpty with a Range{,From,To,Full}:
fn foo(a: Vec<u8>, b: NonEmpty<u8>) {
let _ = a[5..];
let _ = b[5..]; // mismatched types expected type `usize` found struct
// `std::ops::RangeFrom<{integer}>`
}
- Dominant language
- Rust
- Stars
- 74
- Forks
- 30
- 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 cloudhead/nonempty
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in cloudhead/nonempty
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