| Age | Commit message (Collapse) | Author | Lines |
|---|
|
The book was located under 'src/doc/trpl' because originally, it was
going to be hosted under that URL. Late in the game, before 1.0, we
decided that /book was a better one, so we changed the output, but
not the input. This causes confusion for no good reason. So we'll change
the source directory to look like the output directory, like for every
other thing in src/doc.
|
|
in favor of just expect()
Fixes #29506
|
|
Fixes #27917
|
|
|
|
|
|
'work' can refer to the game itself, ie, 'this compiles but the game isn't finished,'
so 'compile' is a more clear way to describe the problem.
Thanks jhun on irc
|
|
Clarifications for those new to Rust and Cargo:
* It's a good idea to get rid of the original `main.exe` in project root
* Slight clarification on the use of `main.rs` vs `lib.rs`
* Clarify that the TOML file needs to be in project root
|
|
Guessing Game states that "Rust only imports a few things into every
program, the ‘prelude’". That isn't strictly true. That is all it
imports by default and the change clarifies that point.
|
|
|
|
We weren't explicit enough about Cargo's default version behavior.
For rust-lang/rust at least,
Fixes #26482
|
|
|
|
I consider that this version has a better reading fluency, instead of having a period between clauses
|
|
|
|
This adds strictly more information to the source files and reduces the
need for customized tooling to render the book.
(While this should not change the output of _rustbook_, it is very
useful when rendering the sources with external tools like Pandoc.)
|
|
r? @steveklabnik
|
|
|
|
|
|
Noticed this while perusing the docs
|
|
|
|
|
|
|
|
Remove an rogue 'is' and fix some line wrapping.
|
|
Didn't realise 0.3.0 referred to all 0.3.x versions! Fixed my mistakes. Should have just updated the Cargo.toml now.
|
|
changed paragraphs with discussion of Cargo.lock file to agree with rand version 0.3.0 in the Cargo.tom file.
|
|
Following paragraph says "we've used `*` which..." but code says "rand=\"0.3.0\""
|
|
|
|
Remove printing of secret number at final source.
|
|
Edit version of #25150.
This commit depends on #25148.
|
|
Let me know if I didn't follow correct procedure - seems a trivial change and no one that can be automatically tested.
|
|
|
|
Remove printing of secret number at final source.
|
|
This commit depends on #25148.
|
|
|
|
https://github.com/rust-lang/rust/pull/25080/files#r29634986
|
|
This also made me realize that I wasn't using the correct term,
'associated functions', rather than 'static methods'. So I corrected
that in the method syntax chapter.
|
|
Fixes #22518
|
|
example that actually does use an Option
|
|
The text is referring to the io module despite the code using the old_io module.
|
|
|
|
This commits adds an associated type to the `FromStr` trait representing an
error payload for parses which do not succeed. The previous return value,
`Option<Self>` did not allow for this form of payload. After the associated type
was added, the following attributes were applied:
* `FromStr` is now stable
* `FromStr::Err` is now stable
* `FromStr::from_str` is now stable
* `StrExt::parse` is now stable
* `FromStr for bool` is now stable
* `FromStr for $float` is now stable
* `FromStr for $integral` is now stable
* Errors returned from stable `FromStr` implementations are stable
* Errors implement `Display` and `Error` (both impl blocks being `#[stable]`)
Closes #15138
|
|
|
|
"Idiomatic code should not use extra whitespace in the middle of a line to provide alignment."
http://aturon.github.io/style/whitespace.html
I realize the linked page still needs an RFC, but the docs should be written in accordance with the guidelines nevertheless.
|
|
uint was recently deprecated, so in following the use of i32 at first,
replace all references to uint with u32.
Also change literals from e.g. 100u to 100, so that they are no longer
usize.
|
|
This commit is an attempt to standardize the use of punctuation and
formatting in "The Rust Programming Language" as discussed in #19823.
- Convert bold text to italicized textcwhen referring to terminology.
- Convert single-quoted text to italicized or double-quoted text,
depending on context.
- Use double quotes only in the case of scare quotes or quotations.
|
|
|
