- 05 8月, 2015 2 次提交
-
-
由 Brian Anderson 提交于
-
由 bors 提交于
For #27501 r? @steveklabnik
-
- 04 8月, 2015 24 次提交
-
-
由 bors 提交于
- Successful merges: #27397, #27398, #27460, #27470, #27491, #27498, #27502 - Failed merges:
-
由 Manish Goregaokar 提交于
this grammar isn't correct this should also get backported to beta /cc @brson
-
由 Manish Goregaokar 提交于
r? @Gankro
-
由 Manish Goregaokar 提交于
-
-
由 Manish Goregaokar 提交于
- Fix #26968 by noting the difference between ".." and "_" more explicitly - Change one of the examples to show the match-all behaviour of ".." - Merge "Ignoring variants" and "Ignoring bindings" sections into the latter r? @steveklabnik
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
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
-
由 bors 提交于
Fixes #27467.
-
由 bors 提交于
Closes #27412 r? @brson
-
由 bors 提交于
This test case has been removed a while ago because it allegedly was broken. But I don't think it is (at least I couldn't reproduce any failure on Linux). Let's give it another chance `:)`
-
由 Matt Friedman 提交于
-
由 Eli Friedman 提交于
Fixes #27467.
-
由 bors 提交于
After #26694, the overloaded operator and "impl not known at method lookup time" cases started triggering the lint. I've also added checks for overloaded autoderef and method calls via paths (i.e. `T::method()`). All new 8 test cases did not trigger the lint before #26694. r? @huonw
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 bors 提交于
After this change, the only remaining symbol we are pulling from libgcc on Win64 is `__chkstk_ms` - the stack probing routine.
-
由 Jonathan Hansford 提交于
-
由 bors 提交于
Fixes #25022 This adapts the deriving mechanism to not repeat bounds for the same type parameter. To give an example: for the following code: ```rust #[derive(Clone)] pub struct FlatMap<I, U: IntoIterator, F> { iter: I, f: F, frontiter: Option<U::IntoIter>, backiter: Option<U::IntoIter>, } ``` the latest nightly generates the following impl signature: ```rust impl <I: ::std::clone::Clone, U: ::std::clone::Clone + IntoIterator, F: ::std::clone::Clone> ::std::clone::Clone for FlatMap<I, U, F> where I: ::std::clone::Clone, F: ::std::clone::Clone, U::IntoIter: ::std::clone::Clone, U::IntoIter: ::std::clone::Clone ``` With these changes, the signature changes to this: ```rust impl <I, U: IntoIterator, F> ::std::clone::Clone for FlatMap<I, U, F> where I: ::std::clone::Clone, F: ::std::clone::Clone, U::IntoIter: ::std::clone::Clone ``` (Nothing in the body of the impl changes) Note that the second impl is more permissive, as it doesn't have a `Clone` bound on `U` at all. There was a compile-fail test that failed due to this. I don't understand why we would want the old behaviour (and nobody on IRC could tell me either), so please tell me if there is a good reason that I missed.
-
由 Steve Klabnik 提交于
this grammar isn't correct
-
由 Michael Woerister 提交于
-
由 Simonas Kazlauskas 提交于
-
由 Alexis Beingessner 提交于
-
由 bors 提交于
-
- 03 8月, 2015 14 次提交
-
-
由 Guillaume Gomez 提交于
-
由 bors 提交于
Inspired by https://github.com/rust-lang/rust/issues/27484
-
由 Tshepang Lekhonkhobe 提交于
-
由 Alexis Beingessner 提交于
-
由 Jonathan Hansford 提交于
-
由 Guillaume Gomez 提交于
-
由 Vadim Chugunov 提交于
-
由 bors 提交于
-
由 bors 提交于
- Successful merges: #27464, #27473 - Failed merges:
-
由 Manish Goregaokar 提交于
This removes some of the more casual language. The only outright goofiness I couldn't bear to remove is "these modules are the bedrock upon which all of Rust is forged, and they have mighty names like `std::slice` and `std::cmp`", which I believe the greatest sentence I have ever created.
-
由 Manish Goregaokar 提交于
Because Markdown.
-
由 Agoston Szepessy 提交于
-
由 bors 提交于
I found that the book had little information for `loop`s and `loop` label so I've added some.
-
由 Brian Anderson 提交于
-