| Age | Commit message (Collapse) | Author | Lines |
|
This commit implements documentation generation of the nomicon, the book, the
style guide, and the standalone docs. New steps were added for each one as well
as appropriate makefile targets for each one as well.
|
|
This commit is the result of the FCPs ending for the 1.8 release cycle for both
the libs and the lang suteams. The full list of changes are:
Stabilized
* `braced_empty_structs`
* `augmented_assignments`
* `str::encode_utf16` - renamed from `utf16_units`
* `str::EncodeUtf16` - renamed from `Utf16Units`
* `Ref::map`
* `RefMut::map`
* `ptr::drop_in_place`
* `time::Instant`
* `time::SystemTime`
* `{Instant,SystemTime}::now`
* `{Instant,SystemTime}::duration_since` - renamed from `duration_from_earlier`
* `{Instant,SystemTime}::elapsed`
* Various `Add`/`Sub` impls for `Time` and `SystemTime`
* `SystemTimeError`
* `SystemTimeError::duration`
* Various impls for `SystemTimeError`
* `UNIX_EPOCH`
* `ops::{Add,Sub,Mul,Div,Rem,BitAnd,BitOr,BitXor,Shl,Shr}Assign`
Deprecated
* Scoped TLS (the `scoped_thread_local!` macro)
* `Ref::filter_map`
* `RefMut::filter_map`
* `RwLockReadGuard::map`
* `RwLockWriteGuard::map`
* `Condvar::wait_timeout_with`
Closes #27714
Closes #27715
Closes #27746
Closes #27748
Closes #27908
Closes #29866
|
|
|
|
See https://doc.rust-lang.org/book/unsafe.html#what-does-safe-mean for the book version of these points which already contain the T.
|
|
|
|
|
|
|
|
Refinement of paragraph referenced by [this issue](https://github.com/rust-lang/rust/issues/31927).
The paragraph in question had been adjusted already, but I've made some further clarifications which should help with readability and not leave the reader any `dangling pointers`.
|
|
See http://www.ietf.org/rfc/rfc2119.txt
|
|
`continue` expression's description mentioned `break` instead of `continue`
|
|
issue](https://github.com/rust-lang/rust/issues/31927)
|
|
It appears in the examples, but is not covered by any of the cases
in the prose description.
|
|
`continue` expression's description mentioned `break` instead of `continue`
Signed-off-by: benaryorg <binary@benary.org>
|
|
|
|
It appears in the examples, but is not covered by any of the cases
in the prose description.
|
|
As a Rust newbie, I found the book's explanation for why the `filter` closure gets a reference very confusing, and tried to figure out why `filter` is somehow less consumptive than `map` -- but it isn't; that's controlled by `iter`/`into_iter`. I flailed around for a while until @habnabit explained it to me, and in retrospect it is quite obvious :-)
|
|
|
|
Reference implied that use declarations may appear *only* at the top of blocks and modules, but it is not the case, and the following is valid:
```Rust
fn foo() {
let x = 92;
use baz::bar;
}
```
r? @steveklabnik
|
|
I sure hope this fix is right
cc @steveklabnik
|
|
|
|
|
|
|
|
|
|
|
|
|
|
See title and diff for more information.
|
|
|
|
This commit implements documentation generation of the nomicon, the book, the
style guide, and the standalone docs. New steps were added for each one as well
as appropriate makefile targets for each one as well.
|
|
Closes #31554.
Contributes to #29380.
|
|
|
|
In the Rust code above this block of compiler output, the function is called print_sum, so use the same function name in the error message.
|
|
In the Rust code above, the function is called print_sum, so use the
same function name in the error message.
|
|
|
|
This file is unused since #27789
|
|
I feel sorry for bothering you with such a literally one character changes. If it is counter productive feel free to point it out in the comments, that would be totally understandable. I could try to pack such a changes together in one PR to make them less distractive.
r? @steveklabnik
|
|
Not everyone knows this convention. We could just rename the variables in the
example, but since this notation is commonly used it's a good opportunity to
introduce it.
r? @steveklabnik
|
|
This is a minor change. Please see title. IMO this is important since this is the first instance when we talk about allocating a vector. Not saying that it is allocated on the stack here leaves room for speculation and this might put off some people (they might not even read the later sections which go into more detail about this).
|
|
|
|
of doing out of bounds accesses.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The code sections shouldn't be inside a ```text block.
|
|
|
|
|
|
Remove unnecessary cloning and conversions. Expand tabs left in examples.
|