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.

Sign up for GitHub

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

Jump to bottom

"Getting started" page in the book mentions "crates" before explaining what a crate is #30825

Closed
K900 opened this issue Jan 11, 2016 · 2 comments
Closed

"Getting started" page in the book mentions "crates" before explaining what a crate is #30825

K900 opened this issue Jan 11, 2016 · 2 comments

Comments

@K900
Copy link

K900 commented Jan 11, 2016

https://doc.rust-lang.org/nightly/book/getting-started.html

With simple projects, Cargo doesn't bring a whole lot over just using rustc, but it will become useful in future. With complex projects composed of multiple crates, it’s much easier to let Cargo coordinate the build. With Cargo, you can just run cargo build, and it should work the right way.

The concept of crates is only (properly) introduced in the next chapter.
@flukejones flukejones mentioned this issue Jan 12, 2016
Merged
@flukejones
Copy link
Contributor

Created pull request which hopefully addresses the issue.

Manishearth added a commit to Manishearth/rust that referenced this issue Jan 15, 2016
@Manishearth
Rollup merge of rust-lang#30836 - Luke-Nukem:master, r=steveklabnik
d9d902e 
Ref issue [30825](rust-lang#30825)

This commit should suffice to add a concise introduction to the concept of crates.
My only worry, is that it is maybe too concise; but, the book seems to be written with the understanding that the new Rust user is coming from another language, and so will understand what a Library or Code Package is.
@steveklabnik
Copy link
Member

This was fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@steveklabnik @K900 @flukejones