Rustlings 6.5.0 turns compiler errors into a guided practice loop
Rustlings 6.5.0 is a terminal program wrapped around small, deliberately incomplete Rust files. You find a TODO or todo!(), edit the code, and let the tool compile or test it again. Watch mode advances through a prescribed order and offers hints when you get stuck. The project recommends doing this beside the official Rust Book, which is the right expectation: Rustlings supplies repetition and immediate feedback, while the book carries most of the conceptual explanation.
The repository contains 25 numbered topic directories from introduction through async, plus quizzes. The sequence covers variables, functions, collections, ownership, error handling, generics, traits, lifetimes, tests, iterators, smart pointers, threads, macros, Clippy, and conversions. Each topic has a short README with reading links. Completed official exercises unlock solution content, and the project warns that those files show one possible answer rather than a canonical style.
What happened when we ran it
Our sandbox installed commit a650509 in 25 seconds and pulled 67 packages. The build then succeeded in 29 seconds. Cargo test ran for 53 seconds before exiting with code 101: 20 tests passed and 6 failed out of 26. The final log excerpt showed the integration suite at 5 passed and 3 failed, followed by Cargo's instruction to rerun --test integration_tests.
The failing excerpt named init, run_compilation_success, and run_test_success, and said tests/test_exercises/exercises/test_success.rs ran with errors. It did not include the underlying diagnostic, so blaming a missing tool, terminal behavior, or the fresh container would be guesswork. The safe conclusion is narrower: the 0.5 MB checkout installed and built, but its full maintainer test command was not green in our 3-CPU, 12 GB Debian sandbox.
Rust 1.88 and a system linker are the real entry requirements
Release v6.5.0 raised the minimum supported Rust version to 1.88 and moved the project to Rust edition 2024. Installation is a normal cargo install rustlings, followed by rustlings init. The setup page also calls out system requirements that beginners can miss: Linux needs GCC for linking, while macOS needs Xcode and its developer tools. Initialization now checks that Clippy is present before creating the exercise workspace.
There are no accounts, API keys, databases, or background services in the standard path. After initialization, you enter the generated directory and run one command to start watch mode. Rustlings recompiles the current exercise after a file change, shows its result, and advances when the work passes. A searchable list lets you inspect progress, jump temporarily, or reset an exercise. For offline study, Rustup can open local copies of the Book and standard library documentation.
Manual mode covers file-watcher failures in containers and WSL
The usage guide anticipates one common runtime snag. If file change detection does not work in a container, virtual machine, or WSL, rustlings --manual-run replaces automatic watching with an explicit r command. That is a reasonable fallback, though it removes some of the instant feedback that makes the tool pleasant. Rustlings also expects a modern terminal; Windows users are directed to Windows Terminal, while VS Code with rust-analyzer is the general editor recommendation.
Version 6.4.0 added search to the exercise list, a check-all command, individual resets, terminal resizing work, and parallel final checks. The unreleased changelog continues with automatic editor opening in VS Code or Zellij and Windows workspace fixes. These are small usability changes aimed at the actual study loop. They also show why learners should install a current release instead of relying on an old package from a system distribution.
Four listed translations live in separate community repositories
The community page lists 4 translated exercise sets: Japanese, Simplified Chinese, Ukrainian, and Korean. The same Rustlings binary can run them after you clone their repositories. Teachers can create a fresh set with rustlings dev new, describe exercises and hints in info.toml, add dependencies, and run rustlings dev check against supplied solutions. Community solutions are visible from the start, unlike the delayed official solution flow.
That extension path is useful for a workshop or company curriculum, but it remains a Git repository workflow. There is no documented cohort dashboard, submission queue, authentication layer, or instructor analytics service. A teacher owns distribution and progress tracking. The course is also intentionally English-first in the main repository; translation projects are maintained elsewhere, and the open German translation proposal from September 2026 shows that language coverage depends on community authors.
An August 30 push and 34 open threads show active upkeep
GitHub recorded 64,092 stars, 25 open issues, and 9 open pull requests when checked. The last push was August 30, 2026, and recent activity included a Windows build improvement, exercise edits, and translation discussion. Release v6.5.0 dates to August 21, 2025, but the later push and current issue work rule out calling the project stale merely because a newer tag has not appeared. The long changelog reaches back through the 6.x rewrite and earlier releases.
Rust by Example is better for readers who want explanations and runnable browser snippets. Mainmatter's 100 Exercises To Learn Rust offers a more course-like sequence, while Exercism adds a hosted submission and feedback model. Rustlings is the best of these for a learner already committed to the Rust Book who wants the compiler involved every few minutes. Our 6 failed tests deserve investigation, but they do not erase the quality of that daily learning loop.