rust/src/test/ui/issues/issue-16725.rs

// aux-build:issue-16725.rs

extern crate issue_16725 as foo;

fn main() {
    unsafe { foo::bar(); }
    //~^ ERROR: function `bar` is private
}
Moved and renamed ui issue tests. 2018-11-04 22:00:03 -06:00			`// aux-build:issue-16725.rs`
rustc: Encode the visibility of foreign items The privacy pass of the compiler was previously not taking into account the privacy of foreign items, or bindings to external functions. This commit fixes this oversight by encoding the visibility of foreign items into the metadata for each crate. Any code relying on this will start to fail to compile and the bindings must be marked with `pub` to indicate that they can be used externally. Closes #16725 [breaking-change] 2014-08-24 19:05:47 -05:00
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_16725 as foo;`
rustc: Encode the visibility of foreign items The privacy pass of the compiler was previously not taking into account the privacy of foreign items, or bindings to external functions. This commit fixes this oversight by encoding the visibility of foreign items into the metadata for each crate. Any code relying on this will start to fail to compile and the bindings must be marked with `pub` to indicate that they can be used externally. Closes #16725 [breaking-change] 2014-08-24 19:05:47 -05:00
			`fn main() {`
			`unsafe { foo::bar(); }`
			//~^ ERROR: function `bar` is private
			`}`