Allocator adaptors for building strings and vectors with shared ownership.
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Assuming allocator support, and P<T, A=Heap> where P<T> is one of Box<T>, Rc<T>, Vec<T>, String, etc.:
There could be an AsRc<A=Heap> allocator adaptor, which leaves space for a refcount when allocating and resizing an allocation.
We can then build a String<AsRc>, convert it to Box<str, AsRc> and convert that to Rc<str>, without any redundant copies.
This might also make an interesting alternative to polymorphic box: Rc::from(box foo) would work even if box expr: Box<T, A> (but it is even more verbose than Rc::new).
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
No files, tests, or entry points are named. Start by researching Rust allocator support and the proposed AsRc adaptor, including the String, Box, and Rc conversions described here. Done would require a concrete RFC with a settled API, ownership behavior, and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100