allocator-migration
Installation
SKILL.md
Turso Allocator Migration
Use this skill for Turso allocator migration work in core, especially when replacing standard heap collections with crate::alloc aliases or adding fallible allocation paths.
Core Rules
- Use
crate::alloc::*in migrated modules. - Keep call-site names stable:
Vec,Box,HashMap,BTreeSet,Arc, and similar standard names. - Use
Tursofor new allocator-specific names, notLimbo. - Use
cfg(nightly)for nightly allocator behavior, not Cargo features. - Do not change
set_allocatorunless the user explicitly asks. - Keep
ArcandWeakrouted throughcrate::syncfor shuttle compatibility for now. Leave allocator-aware shared pointers as a TODO. - Do not migrate tests to fallible allocation unless they block compilation or the user asks.
Import Pattern
For migrated modules, prefer a single allocator namespace import: