Glob imports ignore extern crate items of parent modules

[crumblingstatue]

It doesn't matter if the extern crate item is public or private, it's ignored in both cases.

Example:

#![feature(libc)]

pub mod foo {
    pub extern crate libc;
    pub mod bar {
        // use foo::libc; // Direct import works
        use foo::*; // Glob import doesn't work
        pub fn bar_fn() {
            let _: libc::c_int;
        }
    }
}

fn main() {
    foo::bar::bar_fn();
}

This gives the error:

<anon>:9:20: 9:31 error: failed to resolve. Use of undeclared type or module `libc`
<anon>:9             let _: libc::c_int;
                            ^~~~~~~~~~~
<anon>:9:20: 9:31 error: use of undeclared type name `libc::c_int`
<anon>:9             let _: libc::c_int;
                            ^~~~~~~~~~~

Note that this is not the same issue as #22145, as it doesn't matter whether the item is public or private.

[durka]

This seems to be fixed in nightly!

[crumblingstatue]

It indeed seems to be fixed.
Can I close this, or should regression tests be added first?

[durka]

Glob imports are famously wonky, so a regression test sounds like a great idea to me. Especially since this seems to have been "fixed by accident" unless I missed another issue.

[jseyfried]

This was fixed in #31362, after which extern crates are treated the same as non-import items.
cc @steveklabnik