rust

Map each await to the state its future owns and identify which value is dropped when another select branch wins. Keep non-cloneable values outside the cancellable send future, use Sender::reserve to acquire capacity, and transfer ownership only at a defined acceptance point.

A safe wrapper must prevent undefined behavior for every safe caller; nullness and length checks alone cannot prove allocation, initialization, aliasing, or lifetime. Keep an unsafe boundary with a precise # Safety contract, or tie returned borrows to a real owner that enforces the foreign lifetime.

Feature unification on a shared normal dependency lets a sibling crate's enabled features mask your crate's missing declaration. Use cargo tree -e features -i to find the activation edge, then declare the required feature on your own dependency and verify with an isolated build.

No, dropping a JoinHandle detaches the task, which keeps running independently. Retain the handle under an owner whose shutdown path awaits it, and treat join errors separately from the task's application-level Result.

Miri checks supported Rust-side memory operations but does not execute arbitrary foreign code. Combine Miri for the Rust boundary with real C-side integration tests for layout, callbacks, allocator pairing, and unwind behavior, and record obligations no tool can establish.

It does not cover Tauri capabilities and plugin configuration, smart-contract semantics, or a web framework's routing APIs; those belong to their own domains. Use it only for concrete Rust ownership, async runtime, unsafe, or Cargo build-contract issues.