mirror of
https://github.com/notohh/rustlings.git
synced 2024-11-22 14:02:22 -05:00
Update welcome and final messages
This commit is contained in:
parent
89e0f64279
commit
5658998c0c
1 changed files with 16 additions and 21 deletions
37
info.toml
37
info.toml
|
@ -1,32 +1,27 @@
|
||||||
format_version = 1
|
format_version = 1
|
||||||
|
|
||||||
welcome_message = """Is this your first time? Don't worry, Rustlings was made for beginners! We are
|
welcome_message = """Is this your first time? Don't worry, Rustlings is made for beginners!
|
||||||
going to teach you a lot of things about Rust, but before we can get
|
We are going to teach you a lot of things about Rust, but before we can
|
||||||
started, here's a couple of notes about how Rustlings operates:
|
get started, here are some notes about how Rustlings operates:
|
||||||
|
|
||||||
1. The central concept behind Rustlings is that you solve exercises. These
|
1. The central concept behind Rustlings is that you solve exercises. These
|
||||||
exercises usually have some sort of syntax error in them, which will cause
|
exercises usually contain some syntax or logic errors which cause the
|
||||||
them to fail compilation or testing. Sometimes there's a logic error instead
|
exercise to fail compilation or testing. It's your job to find all errors
|
||||||
of a syntax error. No matter what error, it's your job to find it and fix it!
|
and fix them!
|
||||||
You'll know when you fixed it because then, the exercise will compile and
|
2. Make sure to have your editor open in the `rustlings/` directory. Rustlings
|
||||||
Rustlings will be able to move on to the next exercise.
|
will show you the path of the current exercise under the progress bar. Open
|
||||||
2. If you run Rustlings in watch mode (which we recommend), it'll automatically
|
the exercise file in your editor, fix errors and save the file. Rustlings will
|
||||||
start with the first exercise. Don't get confused by an error message popping
|
automatically detect the file change and rerun the exercise. If all errors are
|
||||||
up as soon as you run Rustlings! This is part of the exercise that you're
|
fixed, Rustlings will ask you to move on to the next exercise.
|
||||||
supposed to solve, so open the exercise file in an editor and start your
|
3. If you're stuck on an exercise, you can request a hint by typing `h` or `hint`
|
||||||
detective work!
|
followed by ENTER.
|
||||||
3. If you're stuck on an exercise, there is a helpful hint you can view by typing
|
|
||||||
'hint' (in watch mode), or running `rustlings hint exercise_name`.
|
|
||||||
4. If an exercise doesn't make sense to you, feel free to open an issue on GitHub!
|
4. If an exercise doesn't make sense to you, feel free to open an issue on GitHub!
|
||||||
(https://github.com/rust-lang/rustlings/issues/new). We look at every issue,
|
(https://github.com/rust-lang/rustlings). We look at every issue, and sometimes,
|
||||||
and sometimes, other learners do too so you can help each other out!
|
other learners do too so you can help each other out!
|
||||||
|
|
||||||
Got all that? Great! To get started, run `rustlings watch` in order to get the first exercise.
|
|
||||||
Make sure to have your editor open in the `rustlings` directory!
|
|
||||||
"""
|
"""
|
||||||
|
|
||||||
final_message = """We hope you enjoyed learning about the various aspects of Rust!
|
final_message = """We hope you enjoyed learning about the various aspects of Rust!
|
||||||
If you noticed any issues, please don't hesitate to report them to our repo.
|
If you noticed any issues, don't hesitate to report them on Github.
|
||||||
You can also contribute your own exercises to help the greater community!
|
You can also contribute your own exercises to help the greater community!
|
||||||
|
|
||||||
Before reporting an issue or contributing, please read our guidelines:
|
Before reporting an issue or contributing, please read our guidelines:
|
||||||
|
|
Loading…
Reference in a new issue