Skip to content
Select theme

Rust by example

Every article answers a single question with code that compiles. Nothing here has to be read in order — open the article that matches what just broke, read it, and go back to your editor.

Two chapters will save you the most time: the bits that trip everyone up for the things that are simply different, and ownership for the one rule the borrow checker is built on. After that, everything here is fair game — and whether Rust is worth learning at all is a fair question with a fair answer.

Compiler errors is the largest chapter on the site: one article per E-code, with the real compiler output and what it means for the code you wrote. If the message on your screen is an error code, that is the fastest way in.

The project tracks are the other half of the site — twelve series that end with a working tool, a service you can deploy, or firmware running on real hardware.