mirror of
https://github.com/rust-lang/rustlings
synced 2024-11-05 00:00:12 +00:00
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:
commit
45d68d9b39
@ -35,8 +35,11 @@ You want to make sure where in the file you add your exercise. If you're not sur
|
||||
```diff
|
||||
...
|
||||
+ [[exercises]]
|
||||
+ name = "yourTopicN"
|
||||
+ path = "exercises/yourTopic/yourTopicN.rs"
|
||||
+ 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
|
||||
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
|
||||
merge it in!
|
||||
merge it in!
|
||||
|
@ -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:
|
||||
|
||||
```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
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user