You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+74-9Lines changed: 74 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -33,18 +33,83 @@ If you choose to not install the `rustlings` command, just replace `rustlings` w
33
33
34
34
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.
35
35
36
-
Your task is simple. Every exercise contains an error you have to solve in order to make it compile. Running `rustlings 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.
36
+
The task is simple. Most exercises contain an error that keep it from compiling, and it's up to you to fix it! Some exercises are also ran as tests, but rustlings handles them all the same. To run the exercises in the recommended order, execute:
37
37
38
-
`rustlings watch` will rerun this verification every time you save an exercise.
38
+
```bash
39
+
rustlings verify
40
+
```
41
+
42
+
This will try to verify the completion of every exercise in a predetermined order (what we think is best for newcomers). If you don't want to rerun `verify` every time you change a file, you can run:
43
+
44
+
```bash
45
+
rustlings watch
46
+
```
47
+
48
+
This will do the same as verify, but won't quit after running and instead automatically rerun as soon as you change a file in the `exercises/` directory.
49
+
50
+
In case you want to go by your own order, or want to only verify a single exercise, you can run:
39
51
40
-
To compile and run a single exercise you can use `rustlings run <path to the exercise>`.
52
+
```bash
53
+
rustlings run exercises/path/to/exercise.rs
54
+
```
55
+
56
+
Or if it's a `#[test]`:
57
+
58
+
```bash
59
+
rustlings run --test exercises/path/to/exercise_with_test.rs
60
+
```
41
61
42
62
In case you get stuck, there is usually a hint at the bottom of each exercise.
43
63
44
-
### Need help?
64
+
## Testing yourself
65
+
66
+
After every couple of sections, there will be a test that'll test your knowledge on a bunch of sections at once. These tests are found in `exercises/testN.rs`.
67
+
68
+
## Completion
69
+
70
+
Rustlings isn't done; there are a couple of sections that are very experimental and don't have proper documentation. These include:
71
+
72
+
- Errors (`exercises/errors/`)
73
+
- Option (`exercises/option/`)
74
+
- Result (`exercises/result/`)
75
+
- Move Semantics (could still be improved, `exercises/move_semantics/`)
76
+
77
+
Additionally, we could use exercises on a couple of topics:
78
+
79
+
- Structs
80
+
- Better ownership stuff
81
+
-`impl`
82
+
- ??? probably more
83
+
84
+
If you are interested in improving or adding new ones, please feel free to contribute! Read on for more information :)
85
+
86
+
## Contributing
87
+
88
+
### Adding an exercise
89
+
90
+
First step is to add the exercise! Call it `exercises/yourTopic/yourTopicN.rs`, make sure to
91
+
put in some helpful links, and link to sections of the book in `exercises/yourTopic/README.md`.
92
+
93
+
Then, you'll want to make sure it gets verified when you run `rustlings verify`. Open `src/verify.rs` and
0 commit comments