Rust Embedded and IoT

Use this when hardware or edge-device constraints change the normal Rust trade-offs.

Working stance

• Own hardware resources explicitly and keep access paths singular.
• Prefer fixed-size storage and predictable timing over convenience.
• Interrupt and task boundaries are data-ownership boundaries.
• Unsafe code is often justified here, but only with tight invariants.
• Pair this skill with rust-memory-and-state first, then rust-unsafe-and-ffi or rust-performance-and-layout if needed.

Domain pressure