How to Wrap Unsafe Code in a Safe API

Wrap unsafe code in a safe API by defining a public function that internally uses an unsafe block to perform the operation, ensuring the function's public interface guarantees safety invariants.

pub fn safe_operation() -> i32 {
    unsafe {
        // Unsafe logic here, e.g., dereferencing a raw pointer
        let ptr: *const i32 = &42;
        *ptr
    }
}

This pattern isolates the unsafe block within a single function, preventing callers from accessing the unsafe code directly while the compiler enforces that the function maintains memory safety.

Wrapping unsafe code in a safe API lets you use powerful but risky features without exposing that risk to the rest of your program. Think of it like a safety guard on a machine: the dangerous parts are hidden inside a box, and you only interact with the safe buttons on the outside. You use this when you need to do low-level tasks like calling C code or manipulating memory directly, but you want to promise your users that the result is safe.