Unexpected behavior importing nested modules with the same name

[brson]

The following test results in items in the inner foo not being resolved even though the compiler let us import foo::foo

import foo::foo;

mod foo {  
  mod foo {
    fn baz() {
    }
  }
}

fn main() {
  // error: unresolved name: baz                                                                         
  foo::baz();
}

Also, using import foo = foo::foo has the same result.

[marijnh]

Actually, in my view of things this is a problem with the name-collision-detection. It should, once I get around to https://github.com/graydon/rust/issues/369 produce an error about binding 'foo' to two different things in the module.

[brson]

That sounds good to me. I thought they might be related after I logged it.