Sixteen small, ordered, Rustlings-style debugging exercises in robot contexts.
Each file has a TODO, a failure to investigate, tests, and a pointer into
The Rust Programming Language. These labs accompany the Forge Rust
Programming module (Robotics track) — one or two labs per week.
Work on one file at a time:
cargo check --bin ex01_mutability
cargo test --bin ex01_mutabilityDo not run an unqualified cargo test until every exercise is fixed — Cargo
will try to compile all unfinished binaries.
For every lab, record in your lesson journal:
- Predict — before compiling, underline the suspect line and predict the outcome.
- Observe — save the smallest relevant diagnostic or failing assertion.
- Translate — state what Rust or the test is claiming, in your own words.
- Hypothesize — name one cause and one change that would distinguish it from an alternative.
- Change — make ONE conceptual change (formatting doesn't count).
- Verify — run the named test, then one additional case you chose.
- Explain — why does the repair work, and what tempting repair would only hide the issue?
After the causal fix: cargo fmt --check and
cargo clippy --tests --bin NAME -- -D warnings.
This is a course companion inspired by Rustlings,
not a fork. The module also uses the upstream Rustlings runner (cargo install rustlings) for general practice sets — your weekly lesson tells you which
Rustlings sections and which of these labs to do.