rust/src/test/compile-fail/issue-511.rs

use std;
use cmp::Eq;

fn f<T:Eq>(&o: Option<T>) {
    assert o == option::None;
}

fn main() {
    f::<int>(option::None);
    //~^ ERROR taking mut reference to static item
    //~^^ ERROR illegal borrow: creating mutable alias to aliasable, immutable memory
}
Add test for issue #511. Closes #511 2011-09-23 00:50:12 -05:00			`use std;`
test: "import" -> "use" 2012-09-05 14:32:05 -05:00			`use cmp::Eq;`
Add test for issue #511. Closes #511 2011-09-23 00:50:12 -05:00
rustc: Make `<` and `=` into traits 2012-08-27 18:26:35 -05:00			`fn f<T:Eq>(&o: Option<T>) {`
Camel case the option type 2012-08-20 14:23:37 -05:00			`assert o == option::None;`
Add test for issue #511. Closes #511 2011-09-23 00:50:12 -05:00			`}`

			`fn main() {`
Camel case the option type 2012-08-20 14:23:37 -05:00			`f::<int>(option::None);`
change the test suite `//! kind` syntax to `//~ kind` in order to avoid a conflict with the new single-line-sugared-inner-doc-comment (`//! ...`). 2012-06-30 06:23:59 -05:00			`//~^ ERROR taking mut reference to static item`
Fix #2979: inference for lifetimes of & expressions 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. 2012-07-26 10:51:57 -05:00			`//~^^ ERROR illegal borrow: creating mutable alias to aliasable, immutable memory`
rustc: Make `<` and `=` into traits 2012-08-27 18:26:35 -05:00			`}`