Find a file
olivia hugger 9996d4e139
Merge pull request #103 from Delet0r/sub_readme
Changed Rust Book versions in links to 2018
2018-11-27 14:05:32 +01:00
exercises Changed Rust Book versions in links to 2018 2018-11-27 10:54:01 +01:00
src Add watch mode, and don't panic on clean failure 2018-11-26 12:45:29 +01:00
.gitignore remove and ignore .DS_Store 2018-11-14 19:24:11 +01:00
Cargo.toml Add watch mode, and don't panic on clean failure 2018-11-26 12:45:29 +01:00
default_out.md add markdown output for default command 2018-11-26 11:10:38 +01:00
ex6.rs Add exercise for creating references in patterns 2018-10-31 04:01:42 +01:00
LICENSE Update LICENSE year. 2016-03-27 15:57:49 -04:00
README.md Created sub READMEs for CLI only version 2018-11-26 16:43:42 +01:00

rustlings

Greetings and welcome to rustlings. This project contains small exercises to get you used to reading and writing code. This includes reading and responding to compiler messages!

How to get started

To use rustlings you have to have rust installed on your machine. If you already have it, you can clone the repo to your local environment with:

git clone https://github.com/rustlings/rustlings.git

To run rustlings you can either use cargo run <subcommand> or you can install rustlings on your machine by running cargo install --path <path to the rustlings repo> (NOTE: for rustling to function you have to be in the directory of the repo).

Doing exercises

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.

Your task is simple every exercise contains an error you have to solve, in order to make it compile.

Running rustlings with the subcommand verify will compile every exercise in the recommended order. It will stop at the first exercise that didn't compile and show you the error to be solved.

If you want to run a single exercise, you can use the subcommand run <path to the exercise>.

When you struggle to solve the error, there is usually a tip at the bottom of each exercise.