Comparing Your Rust Driver with the C Driver of the Same Device
The same virtual card has a driver written in C, and reading the two side by side is a translation exercise that shows what the Rust version buys you. You line up the matching parts — matching the device, mapping its registers, handling the interrupt, releasing everything — and ask, for each thing the C version must remember to undo by hand, where that undoing happens in Rust and who guarantees it. After it you can read C driver code well enough to learn from the enormous library of existing drivers, and you can say concretely, not as a slogan, what the compiler is checking for you.
Questions this Concept answers
- When the Rust version of the same driver has no cleanup ladder, what is actually doing that work?
This Concept is waiting for its first lesson!
The same virtual card has a driver written in C, and reading the two side by side is a translation exercise that shows what the Rust version buys you. You line up the matching parts — matching the device, mapping its registers, handling the interrupt, releasing everything — and ask, for each thing the C version must remember to undo by hand, where that undoing happens in Rust and who guarantees it. After it you can read C driver code well enough to learn from the enormous library of existing drivers, and you can say concretely, not as a slogan, what the compiler is checking for you.
Are you a teacher? Sign in to start contributing.
Sign In