diff options
| author | bors <bors@rust-lang.org> | 2016-01-11 06:40:58 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2016-01-11 06:40:58 +0000 |
| commit | 69e1f57dfbd32a1a342d696a3e79624da97ebe1b (patch) | |
| tree | 42571100253fd85695b9a256399e9476c2974253 /src/test/compile-fail/const-eval-overflow.rs | |
| parent | d70ab2bdf16c22b9f3ff0230089b44855e3f1593 (diff) | |
| parent | 834fb17e9476204dbd5723cd2cc3617bf848b9e9 (diff) | |
| download | rust-69e1f57dfbd32a1a342d696a3e79624da97ebe1b.tar.gz rust-69e1f57dfbd32a1a342d696a3e79624da97ebe1b.zip | |
Auto merge of #30295 - jseyfried:fix_extern_crate_duplicate, 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.
Diffstat (limited to 'src/test/compile-fail/const-eval-overflow.rs')
0 files changed, 0 insertions, 0 deletions
