Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upIntro of rustc in docs should mention debug/optimization #22330
Comments
steveklabnik
added
the
A-docs
label
Feb 14, 2015
This comment has been minimized.
This comment has been minimized.
|
You can't mention every possibe aspect all at once. The introduction already takes a very long time to get to actual code, and I don't want to pollute it any further. |
steveklabnik
closed this
Feb 17, 2015
This comment has been minimized.
This comment has been minimized.
|
@steveklabnik Would you be open to an entirely new section that is referenced from the intro location? If so, I'll create that issue. |
This comment has been minimized.
This comment has been minimized.
|
I would like an "optimizing and debugging Rust" chapter in the book, but I'm not tracking chapter feature requests currently. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tanadeau commentedFeb 14, 2015
Mentions of the use of the rustc binary in the docs (such as the "Hello, World!" section in the Rust book) should mention that no optimizations are performed unless the
-Oor similar flag is given. They should also give a quick overview of the debug/optimization differences and use-cases. This distinction is often new to users coming from JIT'ed/interpreted languages.