Roadmap & Next Steps

To be entirely candid, the direct, alloc-specific infrastructure is now largely in place. The immediate next steps within the alloc crate itself mostly involve routine maintenance: reviewing the recently merged patches, ironing out edge cases, and fixing any newly discovered bugs.

The true path forward for alloc does not involve writing more alloc-specific code; it requires advancing the upstream core support. Because alloc is fundamentally built on top of core, any structural limitations in core inherently bottleneck alloc.

Therefore, the most impactful contribution to alloc right now is helping the gccrs team complete the missing core infrastructure.

As the compiler’s support for core matures, the future roadmap for alloc will naturally unfold:

• Phasing Out the Mock: The temporary mock core used in our test suite will be gradually removed.
• End-to-End Testing: The alloc test suite will be updated to compile against the actual standard core crate, pushing past the name resolution phase.
• Replacing Stubs: The temporary stubs and workarounds we registered to unblock development will be cleanly replaced with their complete backend implementations.