rust/src/test/run-pass/issues/issue-12612.rs

// run-pass
#![allow(unused_imports)]
// aux-build:issue_12612_1.rs
// aux-build:issue_12612_2.rs

// pretty-expanded FIXME #23616

extern crate issue_12612_1 as foo;
extern crate issue_12612_2 as bar;

mod test {
    use bar::baz;
}

fn main() {}
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 07:18:55 -05: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 16:51:35 -05:00			`#![allow(unused_imports)]`
rustc: Add support for `extern crate foo as bar` The compiler will now issue a warning for crates that have syntax of the form `extern crate "foo" as bar`, but it will still continue to accept this syntax. Additionally, the string `foo-bar` will match the crate name `foo_bar` to assist in the transition period as well. This patch will land hopefully in tandem with a Cargo patch that will start translating all crate names to have underscores instead of hyphens. cc #23533 2015-03-19 17:39:03 -05:00			`// aux-build:issue_12612_1.rs`
			`// aux-build:issue_12612_2.rs`
rustc: Disallow importing through use statements Resolve is currently erroneously allowing imports through private `use` statements in some circumstances, even across module boundaries. For example, this code compiles successfully today: use std::c_str; mod test { use c_str::CString; } This should not be allowed because it was explicitly decided that private `use` statements are purely bringing local names into scope, they are not participating further in name resolution. As a consequence of this patch, this code, while valid today, is now invalid: mod test { use std::c_str; unsafe fn foo() { ::test::c_str::CString::new(0 as *u8, false); } } While plausibly acceptable, I found it to be more consistent if private imports were only considered candidates to resolve the first component in a path, and no others. Closes #12612 2014-04-08 16:31:25 -05:00
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 15:13:15 -05:00			`// pretty-expanded FIXME #23616`

rustc: Add support for `extern crate foo as bar` The compiler will now issue a warning for crates that have syntax of the form `extern crate "foo" as bar`, but it will still continue to accept this syntax. Additionally, the string `foo-bar` will match the crate name `foo_bar` to assist in the transition period as well. This patch will land hopefully in tandem with a Cargo patch that will start translating all crate names to have underscores instead of hyphens. cc #23533 2015-03-19 17:39:03 -05:00			`extern crate issue_12612_1 as foo;`
			`extern crate issue_12612_2 as bar;`
rustc: Disallow importing through use statements Resolve is currently erroneously allowing imports through private `use` statements in some circumstances, even across module boundaries. For example, this code compiles successfully today: use std::c_str; mod test { use c_str::CString; } This should not be allowed because it was explicitly decided that private `use` statements are purely bringing local names into scope, they are not participating further in name resolution. As a consequence of this patch, this code, while valid today, is now invalid: mod test { use std::c_str; unsafe fn foo() { ::test::c_str::CString::new(0 as *u8, false); } } While plausibly acceptable, I found it to be more consistent if private imports were only considered candidates to resolve the first component in a path, and no others. Closes #12612 2014-04-08 16:31:25 -05:00
			`mod test {`
			`use bar::baz;`
			`}`

			`fn main() {}`