A struct defined to hold a closure accepts a proc in its constructor

[bstrie]

This seems like it shouldn't be possible:

struct Test<'s> {
    func: 's ||
}

fn main() {
    let test = ~Test { func: proc() {} };
}

...but it compiles just fine on 0.9.

[brson]

Presumably with horrible results? Nominating.

[nikomatsakis]

cc me

[pnkfelix]

Accepting for P-backcompat-lang.

[nikomatsakis]

presumably a symptom of the current semi-hacky integration of proc into rustc

[eddyb]

Can't reproduce anymore, should we close this?

[alexcrichton]

I don't think it should be closed quite yet, the error message is pretty awful:

foo.rs:6:30: 6:39 error: borrowed value does not live long enough
foo.rs:6     let test = ~Test { func: proc() {} };
                                      ^~~~~~~~~
foo.rs:5:11: 7:2 note: reference must be valid for the block at 5:10...
foo.rs:5 fn main() {
foo.rs:6     let test = ~Test { func: proc() {} };
foo.rs:7 }
foo.rs:6:9: 6:41 note: ...but borrowed value is only valid for the statement at 6:8
foo.rs:6     let test = ~Test { func: proc() {} };
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error: aborting due to previous error

Because this no longer compiles successfully, nominating go go from 1.0 backcompat-lang to P-low

[pnkfelix]

Recategorizing as P-low, not on 1.0 milestone.