Empty vec should not allocate
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3
- Forks
- 5
- Avg merge
- 1h 40m
- Merged PRs (30d)
- 11
Description
Currently, SplitVec::new() or SplitVec created with other built-in growth strategies allocate the first fragment. Ideally, an empty vector must not allocate any fragments to avoid unnecessary heap allocation.
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 with SplitVec::new() and the constructors using built-in growth strategies, then trace how the first fragment is created. Verify that an empty SplitVec has no fragments and that allocation begins only after elements are added; run the repository's tests and add coverage for the empty case if needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100