| Age | Commit message (Collapse) | Author | Lines |
|---|
|
http://doc.rust-lang.org/rustdoc.html states that its content was moved to http://doc.rust-lang.org/book/documentation.html
|
|
Also some tidying up of a bunch of crate attributes
|
|
|
|
Use auto deref instead.
|
|
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
|
|
|
|
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
|
|
Use deref coercions instead.
|
|
|
|
|
|
|
|
Lifetime elision with two input references is not clear.
Closes #21284
|
|
|
|
|
|
Lifetime elision with two input references is not clear.
Closes #21284
|
|
|
|
We've had some new people post questions to Discuss, so this should be removed for now. http://discuss.rust-lang.org/t/did-you-mean-to-point-to-discuss-rust-lang-org-as-a-user-forum/1381
|
|
Fixes #16969
|
|
|
|
Fixes #16969
|
|
Lifetime elision documentation was reference a previously existing function
that doesn't exist. After talking with Steve Klabnik, I confirmed the correct
function to be referenced and updated documentation accordingly.
|
|
Fixes #21430
|
|
Compiling won't produce an executable just yet because (as stated in the next
paragraph) there are errors. By removing this sentance, the reader won't get
confused when they expect a successful compile i.e. if they don't read ahead one
paragraph, they are going to be checking their code and wondering why it's not
compiling.
|
|
Updated incorrect error messages, and removed explicit return statements from example code.
|
|
When we moved over to the book, we lost this.
|
|
When we moved over to the book, we lost this.
|
|
|
|
* Include an illustration of a function that accepts two closures.
|
|
Fixes #21430
|
|
Conflicts:
src/libcore/ops.rs
src/librustc_typeck/astconv.rs
src/libstd/io/mem.rs
src/libsyntax/parse/lexer/mod.rs
|
|
|
|
Tiny fix
|
|
r? @FlaPer87
|
|
Slightly change the title to make it look more consistent with other chapters (e.g. Match.)
|
|
|
|
Compiling won't produce an executable just yet because (as stated in the next
paragraph) there are errors. By removing this sentance, the reader won't get
confused when they expect a successful compile i.e. if they don't read ahead one
paragraph, they are going to be checking their code and wondering why it's not
compiling.
|
|
|
|
Multiple people have asked me if this is a reference to Hacker News, and
I _certainly_ don't want to give them that impression.
|
|
After PR #19766 added implicit coersions `*mut T -> *const T`, the explicit casts can be removed.
(The number of such casts turned out to be relatively small).
|
|
From std::markers to std::marker.
|
|
|
|
Having both "Right now" and "at the moment" in the same statement is redundant.
|
|
The reference should be `x`, not `FOO` itself.
|
|
Now both the enum values and the prose describing them mention the values in the same order.
|
|
Multiple people have asked me if this is a reference to Hacker News, and
I _certainly_ don't want to give them that impression.
|
|
These two attributes are used to change the entry point into a Rust program, but
for now they're being put behind feature gates until we have a chance to think
about them a little more. The #[start] attribute specifically may have its
signature changed.
This is a breaking change to due the usage of these attributes generating errors
by default now. If your crate is using these attributes, add this to your crate
root:
#![feature(start)] // if you're using the #[start] attribute
#![feature(main)] // if you're using the #[main] attribute
cc #20064
|
|
|
|
|
|
|
|
From std::markers to std::marker.
|
