Rewriting of a small component from C to Rust
summary
Rewrites a ~2000-line C component into Rust, replacing a single-threaded control loop that runs at about 12 ms with a Rust version compiled via Cargo and using crates for testing and FFI; the port is rewritten in one afternoon and uncovers a hidden allocation failure that had taken three days to find in C. Results: easier mocking and unit tests, compile-time checks preventing uninitialized fields and unchecked results, fewer deadline misses (requirements are a few parts per million), and lower CPU usage according to the uploader.
AI-written summary · about
chapters (22)
- 0:00Start
- 6:51Application Logic
- 12:15Standard Library
- 12:55Posix Library
- 13:20Memory Location
- 13:34Static Memory Allocation
- 13:45Automatic Memory Allocation
- 19:10Testing
- 21:56Why Rust
- 22:12Printf Driven Debugging
- 24:32Implementation
- 25:27Rust Standard Library
- 26:24Memory Handling
- 29:02Dependency Management
- 30:25Unit Test
- 31:28Mocking
- 34:21Should I Use Rust
- 39:06Switching Target Architecture
- 39:38What I Learned from this Experience
- 44:52Which Tools Do You Use To Build the Shared Library and the Header File from Ruscode
- 53:41Do You Suggest Using Rust for Other Uses like Web or Games
- 54:49Did You Notice any Slowdown in Compilation Time for the Comp Component after the Rewrite
