Greetings and welcome to
rustlings. This project contains small exercises to get you used to reading and writing Rust code. This includes reading and responding to compiler messages!
...looking for the old, web-based version of Rustlings? Try here
Alternatively, for a first-time Rust learner, there are several other resources:
- The Book - The most comprehensive resource for learning Rust, but a bit theoretical sometimes. You will be using this along with Rustlings!
- Rust By Example - Learn Rust by solving little exercises! It's almost like
rustlings, but online
Note: If you're on MacOS, make sure you've installed Xcode and its developer tools by typing
You will need to have Rust installed. You can get it by visiting https://rustup.rs. This'll also install Cargo, Rust's package/project manager.
curl -L https://git.io/rustlings | bash # Or if you want it to be installed to a different path: curl -L https://git.io/rustlings | bash -s mypath/
This will install Rustlings and give you access to the
rustlings command. Run it to get started!
In PowerShell, set
Then, you can run:
Start-BitsTransfer -Source https://git.io/rustlings-win -Destination $env:TMP/install_rustlings.ps1; Unblock-File $env:TMP/install_rustlings.ps1; Invoke-Expression $env:TMP/install_rustlings.ps1
To install Rustlings. Same as on MacOS/Linux, you will have access to the
rustlings command after it.
When you get a permission denied message then you have to exclude the directory where you placed the rustlings in your virus-scanner
Basically: Clone the repository, checkout to the latest tag, run
git clone https://github.com/rust-lang/rustlings cd rustlings git checkout tags/4.3.0 # or whatever the latest version is (find out at https://github.com/rust-lang/rustlings/releases/latest) cargo install --force --path .
If there are installation errors, ensure that your toolchain is up to date. For the latest, run:
Then, same as above, run
rustlings to get started.
The exercises are sorted by topic and can be found in the subdirectory
rustlings/exercises/<topic>. For every topic there is an additional README file with some resources to get you started on the topic. We really recommend that you have a look at them before you start.
The task is simple. Most exercises contain an error that keeps them from compiling, and it's up to you to fix it! Some exercises are also run as tests, but rustlings handles them all the same. To run the exercises in the recommended order, execute:
This will try to verify the completion of every exercise in a predetermined order (what we think is best for newcomers). It will also rerun automatically every time you change a file in the
exercises/ directory. If you want to only run it once, you can use:
This will do the same as watch, but it'll quit after running.
In case you want to go by your own order, or want to only verify a single exercise, you can run:
rustlings run myExercise1
In case you get stuck, you can run the following command to get a hint for your exercise:
rustlings hint myExercise1
After every couple of sections, there will be a quiz that'll test your knowledge on a bunch of sections at once. These quizzes are found in
Once you've completed Rustlings, put your new knowledge to good use! Continue practicing your Rust skills by building your own projects, contributing to Rustlings, or finding other open-source projects to contribute to.
If you'd like to uninstall Rustlings, you can do so by invoking cargo and removing the rustlings directory:
cargo uninstall rustlings rm -r rustlings/ # or on Windows: rmdir /s rustlings
If you want to remove Rustlings from your system, there's two steps. First, you'll need to remove the exercises folder that the install script created for you:
rm -rf rustlings # or your custom folder name, if you chose and or renamed it
Second, since Rustlings got installed via
cargo install, it's only reasonable to assume that you can also remove it using Cargo, and
exactly that is the case. Run
cargo uninstall to remove the
cargo uninstall rustlings
Now you should be done!
Rustlings isn't done; there are a couple of sections that are very experimental and don't have proper documentation. These include:
- Errors (
- Option (
- Result (
- Move Semantics (could still be improved,
Additionally, we could use exercises on a couple of topics:
- Better ownership stuff
- ??? probably more
If you are interested in improving or adding new ones, please feel free to contribute! Read on for more information :)
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!