Using mod <name> in <name>.rs leads to "internal compiler error: unexpected failure"

[mike-brown]

The following code snippet:

// foo.rs
mod foo;
fn main() {}

will result in the compiler throwing:

error: internal compiler error: unexpected failure
note: the compiler hit an unexpected failure path. this is a bug

with the top line of the backtrace that the error told me to run being:

rust: task b4d04940 ran out of stack

Removing the mod foo; statement fixes, and is seemingly because of the cyclic import that this causes. Is there a way that self-references using mod can be caught and handled nicely? With something like this sample it's easy to see the error and to debug, but I was chasing a typo in my mod statement for 5 minutes before I found it in my source...

[catamorphism]

It's definitely a bug that this is handled by running out of stack! We need to have a better error message.

[nikomatsakis]

Not critical for 0.6; removing milestone

[graydon]

Reproduced, real. nominating for production ready. It's a bug, but one people will hit.

[Blei]

This has been fixed.

[huonw]

Fixed by #7585.