Avoid introducing run twice in the Rust book
#36878
Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @steveklabnik (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
| @@ -504,6 +504,8 @@ $ cargo run | |||
| Running `target/debug/hello_world` | |||
| Hello, world! | |||
| ``` | |||
| The `run` command comes in handy when you need to rapidly iterate on a | |||
There was a problem hiding this comment.
Missing an empty line before this one.
As it stands, getting-started and guessing-game both introduce `run` as a new command. The second should probably make it clear that the reader has seen it before :)
|
Thanks! @bors: r+ rollup |
|
📌 Commit bcac486 has been approved by |
…n-intro, r=GuillaumeGomez Avoid introducing `run` twice in the Rust book As it stands, getting-started.md and guessing-game.md both introduce `run` as a new command. I switched it so that the 2nd refers back to the first introduction, rather than re-introducing the command. (First ever FOSS PR, sorry if I screwed up anything obvious :) ) r? @steveklabnik
As it stands, getting-started.md and guessing-game.md both introduce
runas a new command. I switched it so that the 2nd refers back to the first introduction, rather than re-introducing the command.(First ever FOSS PR, sorry if I screwed up anything obvious :) )
r? @steveklabnik