Uh oh!
There was an error while loading. Please reload this page.
resolve: fix bug in duplicate checking for extern crates - #30295
Conversation
rust-highfive
commented
Dec 10, 2015
r? @pnkfelix (rust_highfive has picked a reviewer for you, use r? to override) |
jseyfried
commented
Dec 11, 2015
r? @nrc |
nrc
commented
Dec 11, 2015
r+ cc @rust-lang/compiler does this need a Crater run? I think not, but does anyone think we should? |
nagisa
commented
Dec 29, 2015
@nrc ping? |
nrc
commented
Dec 29, 2015
@bors: r+ |
bors
commented
Dec 29, 2015
📌 Commit 0310a7a has been approved by |
bors
commented
Dec 30, 2015
⌛ Testing commit 0310a7a with merge d91bf3f... |
bors
commented
Dec 30, 2015
💔 Test failed - auto-linux-64-nopt-t |
There was a problem hiding this comment.
This cannot be merged anymore because in master, the type of this match statement has changed. While it still merges cleanly, it will not compile.
8ae7d1b to
0c64ddaCompare0c64dda to
834fb17Comparejseyfried
commented
Jan 7, 2016
@nrc rebased |
nrc
commented
Jan 7, 2016
@bors: r+ |
bors
commented
Jan 7, 2016
📌 Commit 834fb17 has been approved by |
bors
commented
Jan 7, 2016
⌛ Testing commit 834fb17 with merge 3917c98... |
bors
commented
Jan 7, 2016
💔 Test failed - auto-linux-64-nopt-t |
brson
commented
Jan 8, 2016
@bors retry |
Fix a bug allowing an item and an external crate to collide so long as the external crate is declared after the item. For example,
```rust
mod core { pub fn f() {} } // This would be an error if it followed the `extern crate`
extern crate core; // This declaration is shadowed by the preceding module
fn main() { core::f(); }
```
This is a [breaking-change], but it looks unlikely to cause breakage in practice, and any breakage can be fixed by removing colliding `extern crate` declarations, which are shadowed and hence unused.bors
commented
Jan 8, 2016
pnkfelix
commented
Jan 9, 2016
@bors retry force |
pnkfelix
commented
Jan 9, 2016
@bors r- |
pnkfelix
commented
Jan 9, 2016
@bors r=nrc force |
bors
commented
Jan 9, 2016
📌 Commit 834fb17 has been approved by |
…e, r=nrc
Fix a bug allowing an item and an external crate to collide so long as the external crate is declared after the item. For example,
```rust
mod core { pub fn f() {} } // This would be an error if it followed the `extern crate`
extern crate core; // This declaration is shadowed by the preceding module
fn main() { core::f(); }
```
This is a [breaking-change], but it looks unlikely to cause breakage in practice, and any breakage can be fixed by removing colliding `extern crate` declarations, which are shadowed and hence unused.bors
commented
Jan 11, 2016
⌛ Testing commit 834fb17 with merge c9b4826... |
bors
commented
Jan 11, 2016
💔 Test failed - auto-win-gnu-64-nopt-t |
alexcrichton
commented
Jan 11, 2016
@bors: retry On Mon, Jan 11, 2016 at 3:09 PM, bors notifications@github.com wrote:
|
bors
commented
Jan 11, 2016
Fix a bug allowing an item and an external crate to collide so long as the external crate is declared after the item. For example,
```rust
mod core { pub fn f() {} } // This would be an error if it followed the `extern crate`
extern crate core; // This declaration is shadowed by the preceding module
fn main() { core::f(); }
```
This is a [breaking-change], but it looks unlikely to cause breakage in practice, and any breakage can be fixed by removing colliding `extern crate` declarations, which are shadowed and hence unused.
Fix a bug allowing an item and an external crate to collide so long as the external crate is declared after the item. For example,
This is a [breaking-change], but it looks unlikely to cause breakage in practice, and any breakage can be fixed by removing colliding
extern cratedeclarations, which are shadowed and hence unused.