1d9ba4c25c
The commented instructions of the exercise ask to use `No description provided` for the description field when calling `easy_ticket` with an invalid description argument. However, the unit test of that behavior compares the description to `Description not provided` instead. Previous exercises in that part also use `Description not provided`. Update the exercise 05_ticket_v2/09_error_trait instructions to use `Description not provided` as an expected default description value when calling `easy_ticket` with no description instead of `No description provided`. |
||
---|---|---|
book | ||
exercises | ||
helpers | ||
.gitignore | ||
.wr.toml | ||
Cargo.lock | ||
Cargo.toml | ||
README.md |
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.