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

// aux-build:issue-21202.rs

extern crate issue_21202 as crate1;

use crate1::A;

mod B {
    use crate1::A::Foo;
    fn bar(f: Foo) {
        Foo::foo(&f);
        //~^ ERROR: method `foo` is private
    }
}

fn main() { }
Moved and renamed ui issue tests. 2018-11-05 04:00:03 +00:00			`// aux-build:issue-21202.rs`
rustc_resolve: Correctly record privacy of methods Loading methods from external crates was erroneously using the type's privacy for each method instead of each method's privacy. This commit fixes that. Closes #21202 2015-01-15 10:49:47 -08: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 15:39:03 -07:00			`extern crate issue_21202 as crate1;`
rustc_resolve: Correctly record privacy of methods Loading methods from external crates was erroneously using the type's privacy for each method instead of each method's privacy. This commit fixes that. Closes #21202 2015-01-15 10:49:47 -08:00
			`use crate1::A;`

			`mod B {`
			`use crate1::A::Foo;`
			`fn bar(f: Foo) {`
			`Foo::foo(&f);`
rustc_resolve: don't handle impl items as if they were modules. 2015-02-20 08:17:05 +02:00			//~^ ERROR: method `foo` is private
rustc_resolve: Correctly record privacy of methods Loading methods from external crates was erroneously using the type's privacy for each method instead of each method's privacy. This commit fixes that. Closes #21202 2015-01-15 10:49:47 -08:00			`}`
			`}`

			`fn main() { }`