| Age | Commit message (Collapse) | Author | Lines |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This updates the book repository, but mostly to include
https://github.com/rust-lang/book/pull/1180
TL;DR: the second edition is close enough to done that we should
universally recommend it over the first edition.
|
|
|
|
Includes https://github.com/rust-lang/book/pull/1088 and
https://github.com/rust-lang/book/commit/62210e326c27697e94ce429c1683dcea4e4887e4
|
|
|
|
Also includes a fix in std::ops
|
|
Fixes #45552.
|
|
This commit updates the bootstrap compiler, bumps the version to 1.23, updates
Cargo, updates books, and updates crates.io dependencies
|
|
Also fixes some stdlib links to the reference which have changed.
|
|
|
|
Primarily to pick up this change:
https://github.com/rust-lang/book/pull/866
...to move this PR forward:
https://github.com/rust-lang/rust/pull/43641
|
|
|
|
Fixes #42632
|
|
|
|
This includes a draft of chapter 20 of the book!
|
|
|
|
The book and the reference have both had changes lately; this integrates
them upstream.
|
|
This includes an important fix for rustc contributors in
https://github.com/rust-lang/book/pull/571
I'm going to update the other ones as well here while we're at it; no
need to spam PRs.
|
|
|
|
Some links needed adjustment to support this new scheme.
|
|
It's all in the external repository now.
|
|
We'll bring this back in with the next commit, as a submodule.
|
|
Remove doc about highlighting code in other languages #40301
This doesn't appear to be true any longer, so removing it to avoid confusion. See #40301
Thoughts:
- may be a good idea to remove "Let's discuss the details of these code blocks.", as there's not much being discussed at this point;
- does `text` still work?
r? @steveklabnik
|
|
Update usages of 'OSX' (and other old names) to 'macOS'.
As of last year with version 'Sierra', the Mac operating system is now
called 'macOS'.
|
|
This was never established as a convention we should follow in the 'More
API Documentation Conventions' RFC:
https://github.com/rust-lang/rfcs/blob/master/text/1574-more-api-documentation-conventions.md
|
|
|
|
|
|
As of last year with version 'Sierra', the Mac operating system is now
called 'macOS'.
|
|
Fix wrong word used in book page "const and static"
|
|
r=steveklabnik
doc: fix inconsistency in error output in guessing-game.md
The line '.expect("failed to read line");' is partly started with a
lower case 'f' and partly with an uppercase one, adding additional
spurious changes to otherwise clean diffs if each sample is
copy-and-pasted over the previous.
This change starts the string with an uppercase everywhere which is in
line with the style of the other strings.
|
|
Fix link in `if let` docs
r? @steveklabnik
|
|
String docs: Add "the"
r? @steveklabnik
|
|
Unit-like structs doc: Improve code sample
r? @steveklabnik
BTW it seems that
```Rust
let p = Proton {};
```
compiles without an error. That's why I didn't add it to the example. It's about consistency anyway.
|
|
|
|
The line '.expect("failed to read line");' is partly started with a
lower case 'f' and partly with an uppercase one, adding additional
spurious changes to otherwise clean diffs if each sample is
copy-and-pasted over the previous.
This change starts the string with an uppercase everywhere which is in
line with the style of the other strings.
|
|
|
|
|
|
|
|
Structs doc: Change "pointers" to "references"
Let's call them "references" instead of "pointers". That's how they're called in chapter 4.9 "References and Borrowing".
r? @steveklabnik
|
|
Make lifetime elision docs clearer
Previously it said
"It's forbidden to allow reasoning about types based on the item signature alone."
I think that sentence is wrong. Rust **uses** the item signatures to perform type inference within the body. I think what's meant is the other way around: It does not infer types for item signatures.
r? @steveklabnik
|
|
Remove unnecessary "for"
|
|
|
|
|
