use-ing an item from the current module causes unresolved use errors.

[brandonson]

Something like this should really produce a better error message:

mod foo {                                                                                           
  extern mod extra;                                                                                 

  use foo::extra;                                                                                       
}

/////////////////////////////////
//The error:
//bug-testing.rs:4:6: 4:16 error: unresolved import
//bug-testing.rs:4   use foo::extra;
//                       ^~~~~~~~~~
//error: aborting due to previous error
//////////////////////////////////

Not sure whether current compiler state makes it difficult to identify this and other reasons for failed resolution, but if it's fairly simple better error messages would be great.

[huonw]

Triage: this appears to be a problem with directly re-importing an from the current module, e.g.

mod foo {
    use foo::bar;
    mod bar {}
}

fn main() {}

gives the same error pointing at use foo::bar. (Adjusting the issue title to reflect this.)

[huonw]

(For comparison, importing something with the same name from a different module is ok:

#[allow(unused_imports)];

mod foo {
    use baz::bar;
    mod bar {}
}
mod baz { pub mod bar {} }

fn main() {}

compiles without a problem.)

[treeman]

Still an issue.

$ rustc -v
rustc 0.12.0-pre (470dbef29 2014-07-25 09:31:10 +0000)

mod foo {
    use foo::bar;
    mod bar {}
}

fn main() {}

Gives error: unresolved import pointing at foo in use foo::bar.

#![allow(unused_imports)]

mod foo {
    use baz::bar;
    mod bar {}
}
mod baz { pub mod bar {} }

fn main() {}

Works. (Updated attribute syntax)

[mukilan]

Both cases (use foo::bar and use baz::bar) now give import bar conflicts with existing submodule error.
I recently fixed the use foo::bar case as a part of the duplicate issue #19498. I'm not sure when the "use baz::bar" case was fixed.
Also see related issue #19609