5d32d03b89
What we now do is to create a region variable for each & expression (and also each borrow). The lifetime of this variable will be checked by borrowck to ensure it is not greater than the lifetime of the underlying data. This both leads to shorter lifetimes in some cases but also longer in others, such as taking the address to the interior of unique boxes tht are rooted in region pointers (e.g., returning a pointer to the interior of a sendable map). This may lead to issue #2977 if the rvalue is not POD, because we may drop the data in trans sooner than borrowck expects us to. Need to work out precisely where that fix ought to occur.
14 lines
262 B
Rust
14 lines
262 B
Rust
fn foo(x: @int) -> fn@() -> &static/int {
|
|
fn@() -> &static/int {&*x} //~ ERROR illegal borrow
|
|
}
|
|
|
|
fn bar(x: @int) -> fn@() -> &int {
|
|
fn@() -> &int {&*x} //~ ERROR illegal borrow
|
|
}
|
|
|
|
fn zed(x: @int) -> fn@() -> int {
|
|
fn@() -> int {*&*x}
|
|
}
|
|
|
|
fn main() {
|
|
} |