Cross-crate enum struct variants exporting bug

[nsf]

The bug occurs only in a cross-crate scenario, probably related to metadata encoding/decoding, have no idea. Here's a quick way to make a mockup:

test.rs:

extern mod testenum;

fn main() {
        let x = testenum::A;
        match x {
                //test.rs:6:2: 6:13 error: `testenum::B` does not name a structure
                //testenum::B{_} => println("oops"),
                testenum::B(_, _) => println("sweet"),
                _ => println("nothing"),
        }
}

.rust/src/testenum/lib.rs

#[link(name = "testenum",
       vers = "0.0")];

pub enum Test {
        A,
        B{f1: int, f2: int},
        C,
}

Then build the crate: rustpkg install testenum. And compile the test.rs: rustc -o test test.rs. It compiles just fine, when it actually shouldn't. Because testenum::B is a struct variant, not a tuple. Uncommenting the struct variant and commenting out the tuple variant results in a compilation error:

test.rs:7:2: 7:13 error: `testenum::B` does not name a structure
test.rs:7               testenum::B{_} => println("oops"),
                        ^~~~~~~~~~~
error: aborting due to previous error

[nsf]

Forgot to add the version, it's fairly recent:

[nsf @ ~]$ rustc --version
rustc 0.8-pre (59ca7a8 2013-08-24 11:02:14 -0700)
host: x86_64-unknown-linux-gnu

[nsf]

There is an existing issue describing a similar bug. #5557

Sorry for not searching before actually submitting, but maybe it's worth bringing the attention to it, as it's not marked with A-metadata tag.

[alexcrichton]

Closed by #9064