Repository navigation
Roadmap 2.0 #150
Description
See #48 for the previous (now-outdated) roadmap.
Core traits, types, and their interactions
- Merge proposed
StaticAllocatortrait & changes toAllocator - Determine the soundness situation w.r.t.
Cloneinteractions- Proposal:
unsafe trait AllocatorClone: Allocator + Clone - Proposal: conditionally-unsafe trait impls
- Proposal:
- Merge a
NativeAllocator<A: StaticAllocator>lang item for LLVM intrinsic interop &noaliasemitting - Explore other proposed extension traits
- Proposals came up for
PartialEqmarking allocator equivalence - do we want something like this? Deallocator?
- Proposals came up for
Beyond GlobalAlloc
- Merge a nightly
GlobalAllocatortrait - Deprecate/hide
GlobalAllocover an edition - Implement
Globalin terms ofNativeAllocator& stop having it be a lang item
Expanded collection types
- Allocator-generic
String - Explore options for more fallible methods on collections
- Move collection types into
core
Allocator-aware pointer types
- Make
Boxno longer fundamental over the allocator - Stabilise the allocator on
Box - Figure out semantics and trait bounds for
Arc/Rc<_, A>- Proposal: Store the allocator inline with the value instead of in the
Rc/Arcitself
- Proposal: Store the allocator inline with the value instead of in the
Stabilisation path
- Stabilise the core
Allocatortrait & minimal functionality around it - Plan out a roadmap for further stabilisations
Meta
- Land an allocator project goal
- Clarify and expand documentation on the allocator trait family
- Clean up old & now-irrelevant issues in this repository
Activity
Rollup merge of rust-lang#156882 - nia-e:stable-allocator, r=clarfonthey
Unrolled build for #156882 in rollup 163189
Rollup merge of #156882 - nia-e:stable-allocator, r=clarfonthey
Rollup merge of rust-lang#156882 - nia-e:stable-allocator, r=clarfonthey
Rollup merge of rust-lang#156882 - nia-e:stable-allocator, r=clarfonthey
Caritajoe18 commentedon Oct 15, 2026
Hello @nia-e
I am an Outreachy applicant. I would like to start contributing by cleaning up old and now-irrelevant issues in this repo.
Do I comment on them directly or tag them here?
Anshumancanrock commentedon Oct 15, 2026
Hi @nia-e , I would like to work on
Proposal: unsafe trait AllocatorClone: Allocator + Clone. Should i start working ?paval-shlyk commentedon Oct 16, 2026
I guess the main issue isn't delivering a proposal, but criticizing it. Your opinion is important, while the development part is pretty trivial.
Joiejoie1 commentedon Oct 16, 2026
Hi @nia-e ,
While taking a look at
boxed.rsand custom allocator support,I noticed an opportunity to add some extra test coverage for
try_clone_from_ref_inusing the System allocator under a few edge cases. Would it be helpful if I put together a small PR for that?kaddujames501-ship-it commentedon Oct 25, 2026
Hello team, I noticed what seems to me like an inconsistency between grow, grow_zeroed, and shrink. grow and shrink both state what happens on Ok and on Err grow_zeroed states neither, and only says it “behaves like grow”. @nia-e Is it intentional?. Thanks!