rust/tests/ui/cross-crate/cross-crate-map-usage-5521.rs

// https://github.com/rust-lang/rust/issues/5521
//@ run-pass
#![allow(dead_code)]
//@ aux-build:aux-5521.rs

extern crate aux_5521 as foo;

fn bar(a: foo::map) {
    if false {
        panic!();
    } else {
        let _b = &(*a)[&2];
    }
}

fn main() {}
Rehome tests/ui/issues/ tests [3/?] 2025-07-13 16:25:27 -04:00			`// https://github.com/rust-lang/rust/issues/5521`
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 14:18:55 +02:00			`//@ run-pass`
Add `#![allow(..)]` as necessary to get re-migrated run-pass tests compiling with clean stderr again. Most were added mechanically. 2018-09-25 23:51:35 +02:00			`#![allow(dead_code)]`
Rehome tests/ui/issues/ tests [3/?] 2025-07-13 16:25:27 -04:00			`//@ aux-build:aux-5521.rs`
Adding tests for closed issues Closes #5521 Closes #9396 Closes #10714 2014-02-03 10:12:26 -08:00
Rehome tests/ui/issues/ tests [3/?] 2025-07-13 16:25:27 -04:00			`extern crate aux_5521 as foo;`
Adding tests for closed issues Closes #5521 Closes #9396 Closes #10714 2014-02-03 10:12:26 -08:00
librustc: Forbid external crates, imports, and/or items from being declared with the same name in the same scope. This breaks several common patterns. First are unused imports: use foo::bar; use baz::bar; Change this code to the following: use baz::bar; Second, this patch breaks globs that import names that are shadowed by subsequent imports. For example: use foo::*; // including `bar` use baz::bar; Change this code to remove the glob: use foo::{boo, quux}; use baz::bar; Or qualify all uses of `bar`: use foo::{boo, quux}; use baz; ... baz::bar ... Finally, this patch breaks code that, at top level, explicitly imports `std` and doesn't disable the prelude. extern crate std; Because the prelude imports `std` implicitly, there is no need to explicitly import it; just remove such directives. The old behavior can be opted into via the `import_shadowing` feature gate. Use of this feature gate is discouraged. This implements RFC #116. Closes #16464. [breaking-change] 2014-08-12 20:31:30 -07:00			`fn bar(a: foo::map) {`
Adding tests for closed issues Closes #5521 Closes #9396 Closes #10714 2014-02-03 10:12:26 -08:00			`if false {`
Rename fail! to panic! https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . \| xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change] 2014-10-09 15:17:22 -04:00			`panic!();`
Adding tests for closed issues Closes #5521 Closes #9396 Closes #10714 2014-02-03 10:12:26 -08:00			`} else {`
Fallout in stdlib, rustdoc, rustc, etc. For most maps, converted uses of `[]` on maps to `get` in rustc, since stage0 and stage1+ disagree about how to use `[]`. 2015-03-21 21:15:47 -04:00			`let _b = &(*a)[&2];`
Adding tests for closed issues Closes #5521 Closes #9396 Closes #10714 2014-02-03 10:12:26 -08:00			`}`
			`}`

			`fn main() {}`