Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cargo run being introduced too late in the Guide #16451

Closed
MatejLach opened this issue Aug 12, 2014 · 1 comment · Fixed by #16474
Closed

cargo run being introduced too late in the Guide #16451

MatejLach opened this issue Aug 12, 2014 · 1 comment · Fixed by #16474
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@MatejLach
Copy link
Contributor

What is the reasoning behind showing the cargo run command to the reader in section 'Crates and Modules' of the Guide? This seems too late to me, since cargo run is very useful for rapid iteration and that is exactly what is happening in section 14 Guessing Game, which is the first bigger project that gets shown in the Guide and I think that it would therefore make sense to introduce the cargo run command in that section.
What's your opinion on this @steveklabnik ?

@steveklabnik
Copy link
Member

I don't remember exactly why, but it wasn't on purpose. I'd support showing it off earlier.

(I think it's that cargo run didn't exist when I started writing, and I added it whenever it actually landed)

bors added a commit that referenced this issue Aug 14, 2014
This fixes #16451.

While moving things around, I also removed a bunch of unnecessary whitespace, however I can put it back in if that's undesired. 

Thanks.
matthiaskrgr pushed a commit to matthiaskrgr/rust that referenced this issue Feb 5, 2024
internal: Work through temporarily allowed clippy lints, part 2

Another follow-up to rust-lang/rust-analyzer#16401.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants