cross-crate class construction fails

[jesse99]

In https://github.com/jdm/rust-socket there is code like this:

export socket_handle;

class socket_handle {
    let sockfd: libc::c_int;
    new(x: libc::c_int) {self.sockfd = x;}
    drop {c::close(self.sockfd);}
}

From a different crate I do:

import socket;
let sock = @socket::socket_handle(fd);

And I get:

src/connection.rs:37:13: 37:39 error: mismatched types: expected function or foreign function but found socket::socket_handle
src/connection.rs:37    let sock = @socket::socket_handle(fd);

This is with rust f676547

Work around for now is to export a function that calls the ctor for me.

(I know instance construction is being actively worked on atm, but it seems like there may be a missing unit test for this case).

[catamorphism]

I'll look at this. I'm suspecting that the problem is that export socket_handle only exports the socket_handle type, and if you deleted the export statement (exporting everything), that would allow you to use the socket_handle constructor from another crate. But that's just a guess.

[brson]

structs also have this problem using the field initialization syntax

[catamorphism]

Couldn't reproduce with 0d7bef4 (I couldn't get rust-socket to compile with the current version of rustc, but I made a self-contained example), so I added the test case.

[pcwalton]

@brson, do you have a test case? I would like to fix this ASAP if it is still a bug.

[pcwalton]

You can't construct cross-crate structs. Embarrassing. Fix underway.