pub use with glob import behaves differently when re-exported vs directly used

I tried this code: Playground

mod foo {
    mod bar {
        pub(crate) fn foo() {
            println!("foo");
        }
    }
    // pub use bar::foo; // error[E0364]:`foo` is only public within the crate, and cannot be re-exported outside
    pub use bar::*;
}

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

I expected to see this happen:

When I use glob imports, I expected to import all importable entities that I can pub use to import directly.

Instead, this happened:

I can use foo::foo() because it is re-exported.

And compiler and clippy(-W clippy::nursery) give many warnings.

Meta

rustc --version --verbose:

rustc 1.86.0 (05f9846f8 2025-03-31) (Arch Linux rust 1:1.86.0-1)
binary: rustc
commit-hash: 05f9846f893b09a1be1fc8560e33fc3c815cfecb
commit-date: 2025-03-31
host: x86_64-unknown-linux-gnu
release: 1.86.0
LLVM version: 19.1.7

Some related link:

https://doc.rust-lang.org/reference/items/use-declarations.html#glob-imports

https://doc.rust-lang.org/error_codes/E0365.html

Start with the linked Playground reproducer and the Reference section on glob imports, then compare the direct pub use case with pub use bar::* and error E0364. Done means the compiler's handling of importable crate-private items is made consistent, with the reported warnings addressed and regression coverage added.