Auto merge of #232 - rust-lang:update-docs, r=fmoko

chore: Update docs for 2.0

Only merge this once we're ready to release 2.0.
This commit is contained in:
bors 2019-11-12 11:07:56 +00:00
commit 45d68d9b39
2 changed files with 11 additions and 3 deletions

View file

@ -35,8 +35,11 @@ You want to make sure where in the file you add your exercise. If you're not sur
```diff ```diff
... ...
+ [[exercises]] + [[exercises]]
+ name = "yourTopicN"
+ path = "exercises/yourTopic/yourTopicN.rs" + path = "exercises/yourTopic/yourTopicN.rs"
+ mode = "compile" + mode = "compile"
+ hint = """
+ Some kind of useful hint for your exercise."""
... ...
``` ```
@ -125,4 +128,4 @@ BREAKING CHANGE: This has to be done because lorem ipsum dolor
Once you open a Pull Request, it may be reviewed or labeled (or both) until Once you open a Pull Request, it may be reviewed or labeled (or both) until
the maintainers accept your change. Then, [bors](https://github.com/bors) will the maintainers accept your change. Then, [bors](https://github.com/bors) will
run the test suite with your changes and if it's successful, automatically run the test suite with your changes and if it's successful, automatically
merge it in! merge it in!

View file

@ -80,10 +80,15 @@ 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: In case you want to go by your own order, or want to only verify a single exercise, you can run:
```bash ```bash
rustlings run exercises/path/to/exercise.rs rustlings run myExercise1
``` ```
In case you get stuck, there is usually a hint at the bottom of each exercise. In case you get stuck, you can run the following command to get a hint for your
exercise:
``` bash
rustlings hint myExercise1
```
## Testing yourself ## Testing yourself