| 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.
|
|
FIxes #29742
|
|
Fixes #29762
|
|
FIxes #29742
|
|
Fixes #29762
|
|
Change conditional perfect to past perfect.
|
|
Fixes #29493
|
|
Fixes #29853
Fixes #29852
While these points are true, we're not going for 100% accuracy here,
this is introductory material. Changing these things would be more
confusing, but it is important to note that we're presenting an
abstraction here.
r? @huonw
|
|
Change conditional perfect to past perfect.
|
|
Fixes #29493
|
|
Fixes #29730
|
|
Fixes #29853
Fixes #29852
While these points are true, we're not going for 100% accuracy here,
this is introductory material. Changing these things would be more
confusing, but it is important to note that we're presenting an
abstraction here.
|
|
|
|
|
|
Fix #29823 by further explaining `&str` and pointing out the
difference between `&str` and `&'static str`.
|
|
Fixes #29730
|
|
|
|
- Check privacy sanity in all blocks, not only function bodies
- Check all fields, not only named
- Check all impl items, not only methods
- Check default impls
- Move the sanity check in the beginning of privacy checking, so others could rely on it
Technically it's a [breaking-change], but I expect no breakage because, well, it's *sane* privacy visitor, if code is broken it must be insane by definition!
|
|
r? @steveklabnik
See #27305
|
|
r? @steveklabnik
|
|
|
|
|
|
|
|
|
|
Fixes #29234
|
|
Fixes #28461
|
|
Now that thread::sleep is a real thing, let's use it
Fixes #29621
r? @bstrie
|
|
Fixes #29591
|
|
|
|
Now that thread::sleep is a real thing, let's use it
Fixes #29621
|
|
Fixes #29591
|
|
Fixes #28461
|
|
[breaking change]
|
|
|
|
anymore.
|
|
in favor of just expect()
Fixes #29506
|
|
Originally, this was my 30 minute introduction, and we eventually made
it the opener to the book. But as #25918 has shown, the example I use
here has some issues. The good news is that Rust makes heap allocation
syntatically expensive, but the bad news is that that means showing
equivalent programs from Rust and other languages is difficult. After
thinking about it, I'm not sure this section is pulling its weight, and
since it has problems, I'd rather just pull it than try to re-write it
right now. I think the book is fine without it.
FIxes #25918
|
|
in favor of just expect()
Fixes #29506
|
|
Originally, this was my 30 minute introduction, and we eventually made
it the opener to the book. But as #25918 has shown, the example I use
here has some issues. The good news is that Rust makes heap allocation
syntatically expensive, but the bad news is that that means showing
equivalent programs from Rust and other languages is difficult. After
thinking about it, I'm not sure this section is pulling its weight, and
since it has problems, I'd rather just pull it than try to re-write it
right now. I think the book is fine without it.
FIxes #25918
|
|
Fixes #29322
|
|
Reword "Writing the logic" paragraph to prevent `unwrap` being confused for a macro (and other small changes to improve the flow of the paragraph).
cc @steveklabnik
|
|
I did some preliminary editing work with No Starch on the first chapter of the book, and here's some of the results. We're going to want to return to this later when @brson etc's new rustup work is done, so this is mostly just a first pass.
But, we agreed that having separate chapters for each of this bit of intro is a bit excessive. So let's move all of this intro stuff into one chapter.
I'd appreciate a careful review of this, as there was also some confusion about some things, which resulted in me taking one huge markdown file apart and splitting it back up, as well as some editor issues, so I _think_ this looks good, but double checking things matters!
/cc @aturon
|
|
|
|
r=nikomatsakis
When referring to the different shared library extensions, specify the OS explicitly.
|
|
Fixes #29322
|
|
Conceptually, this makes more sense as one introductory chapter.
|
|
Reword "Writing the logic" paragraph to prevent `unwrap` being confused
for a macro.
|
|
Lots of little details and things.
|
|
This replaces usage of the (missing) `fatal!` macro with `panic!`.
|
|
When referring to the different shared library extensions, specify the OS explicitly.
|
