Support some of the unstable/unsafe features from `std::Vec`
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 320
- Forks
- 32
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 1
Description
It would be nice if the API mapped closer to std::Vec.
Methods like assume_init or set_len or the ability to use custom allocators are used in a project for which EcoVec is otherwise a perfect fit to reduce memory fragmentation.
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 comparing EcoVec's existing public API with the corresponding std::Vec documentation, focusing on assume_init, set_len, and custom allocator support. Define the safety and compatibility requirements for each requested capability; done means the feasible API changes are implemented with their required validation and documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100