rust/tests/ui/resolve/issue-26545.rs

mod foo {
    pub struct B(pub ());
}

mod baz {
    fn foo() {
        B(());
        //~^ ERROR cannot find function, tuple struct or tuple variant `B` in this scope [E0425]
    }
}

fn main() {}
Prefer accessible paths in 'use' suggestions This fixes an issue with the following sample: mod foo { mod inaccessible { pub struct X; } pub mod avail { pub struct X; } } fn main() { X; } Instead of suggesting both `use crate::foo::inaccessible::X;` and `use crate::foo::avail::X;`, it should only suggest the latter. It is done by trimming the list of suggestions from inaccessible paths if accessible paths are present. Visibility is checked with `is_accessible_from` now instead of being hard-coded. - Some tests fixes are trivial, and others require a bit more explaining, here are my comments: src/test/ui/issues/issue-35675.stderr: Only needs to make the enum public to have the suggestion make sense. src/test/ui/issues/issue-42944.stderr: Importing the tuple struct won't help because its constructor is not visible, so the attempted constructor does not work. In that case, it's better not to suggest it. The case where the constructor is public is covered in `issue-26545.rs`. 2020-06-13 12:58:46 -05:00			`mod foo {`
			`pub struct B(pub ());`
			`}`

			`mod baz {`
			`fn foo() {`
			`B(());`
			//~^ ERROR cannot find function, tuple struct or tuple variant `B` in this scope [E0425]
			`}`
			`}`

			`fn main() {}`