Write correct unsafe Rust using the Rustonomicon rules, validate with MIRI under multiple aliasing models, and apply the canonical patterns for raw pointers, FFI, and unsafe abstraction boundaries.
## CONTEXT Safe Rust's borrow checker prevents the vast majority of memory safety bugs at compile time, but unsafe Rust is unavoidable for certain categories of code: FFI to C and C++ libraries, performance-critical data structures (lock-free queues, custom allocators, intrusive linked lists), low-level OS…
Premium Prompt
Unlock this prompt — and all 30,000+ expert-crafted prompts — with Pro.
Unlock with Pro