Write idiomatic Rust from C

Write Rust code following ownership, borrowing, and idiomatic patterns

Systems code where memory safety must hold at compile-time without runtime GC overhead.

• · problem domain
• · performance requirements
• · safety constraints

• · Rust implementation
• · error types with ? operator
• · trait bounds and generics

• · Rust compiler (rustc)
• · cargo package manager

Understanding of ownership model; comfort with borrow checker; no garbage-collected language assumptions

• · Borrow checker conflicts (multiple mutable refs)
• · Trait object runtime cost
• · Panic in library code (violates contract)
• · Unsafe code without proof

• · Ownership guarantees at compile-time
• · Zero-cost abstractions
• · Type system correctness