Should not be able to declare mod item and type item (e.g. an enum) in same scope

[pnkfelix]

Illustrative code provided by cmr:

mod Foo {
    pub static X: int = 42;
}

#[deriving(Show)]
enum Foo {
    X
}

fn main() {
    println!("{}", Foo::X);
    let x: Foo = X;
    println!("{}", x);
}

The above should not be legal: one should not be able to declare the mod Foo item in the same scope as the enum Foo item.

But the following playpen appears to accept it, at the moment.

[pnkfelix]

Nominating for 1.0, P-backcompat-lang.

[pnkfelix]

(This is relevant to rust-lang/rfcs#94 )

[pnkfelix]

Assigning P-backcompat-lang, to the 1.0 milestone.

[whyisthisfieldhere]

This isn't fully fixed in 0.12:

This generates an error:

#[deriving(Show)]
mod Foo {
    pub static X: int = 42;
}
type Foo = u32;

fn main() {
    println!("{}", Foo::X);
}

While this doesn't: (all that changed is the order of type and mod)

type Foo = u32;

#[deriving(Show)]
mod Foo {
    pub static X: int = 42;
}

fn main() {
    println!("{}", Foo::X);
}

(I'm not too sure if the first example is intended to generate errors or not, but the inconsistency is definitely unexpected)