rust/tests/ui/self/self-shadowing-import.rs

//@ run-pass

mod a {
    pub mod b {
        pub mod a {
            pub fn foo() -> isize { return 1; }
        }
    }
}

mod c {
    use crate::a::b::a;
    pub fn bar() { assert_eq!(a::foo(), 1); }
}

pub fn main() { c::bar(); }
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-pass`
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 13:13:15 -07:00
Ignore current scope when resolving self-shadowing imports That is, for example, import x::y::x, which defines a local x, and thus wouldn't be able to find x::y anymore. Closes issue #624 2011-07-08 16:04:40 +02:00			`mod a {`
test: Remove export from the tests, language, and libraries. rs=deexporting 2013-01-30 15:56:40 -08:00			`pub mod b {`
			`pub mod a {`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 17:06:52 -07:00			`pub fn foo() -> isize { return 1; }`
Ignore current scope when resolving self-shadowing imports That is, for example, import x::y::x, which defines a local x, and thus wouldn't be able to find x::y anymore. Closes issue #624 2011-07-08 16:04:40 +02:00			`}`
			`}`
			`}`

			`mod c {`
Use non-2015 edition paths in tests that do not test for their resolution 2025-06-05 08:41:49 +02:00			`use crate::a::b::a;`
Use `assert_eq!` instead of `assert!` in tests 2015-06-07 21:00:38 +03:00			`pub fn bar() { assert_eq!(a::foo(), 1); }`
Ignore current scope when resolving self-shadowing imports That is, for example, import x::y::x, which defines a local x, and thus wouldn't be able to find x::y anymore. Closes issue #624 2011-07-08 16:04:40 +02:00			`}`

check-fast fallout from removing export, r=burningtree 2013-02-01 19:43:17 -08:00			`pub fn main() { c::bar(); }`