2e2f6b945d
It's generally better practice to handle or propagate errors, rather than panicking in response to them. This edit moves panicking to be the _last_ option introduced, rather than the first. It also adds caveats to avoid doing so, and explicitly mentions propagating as something to consider. |
||
---|---|---|
.github/workflows | ||
book | ||
exercises | ||
helpers | ||
site | ||
.gitignore | ||
.wr.toml | ||
Cargo.lock | ||
Cargo.toml | ||
dprint.json | ||
README.md |
Learn Rust, one exercise at a time
You've heard about Rust, but you never had the chance to try it out?
This course is for you!
You'll learn Rust by solving 100 exercises.
You'll go from knowing nothing about Rust to being able to start
writing your own programs, one exercise at a time.
Note
This course has been written by Mainmatter.
It's one of the trainings in our portfolio of Rust workshops.
Check out our landing page if you're looking for Rust consulting or training!
Getting started
Go to rust-exercises.com and follow the instructions there to get started with the course.
Requirements
- Rust (follow instructions here).
Ifrustup
is already installed on your system, runrustup update
(or another appropriate command depending on how you installed Rust on your system) to make sure you're running on the latest stable version. - (Optional but recommended) An IDE with Rust autocompletion support.
We recommend one of the following:
- RustRover;
- Visual Studio Code with
the
rust-analyzer
extension.
Solutions
You can find the solutions to the exercises in
the solutions
branch of this repository.
License
Copyright © 2024- Mainmatter GmbH (https://mainmatter.com), released under the Creative Commons Attribution-NonCommercial 4.0 International license.