rust/src/test/compile-fail/lambda-mutate.rs

// error-pattern:assigning to upvar
// Make sure we can't write to upvars from fn@s
fn main() {
    let i = 0;
    let ctr = fn@ () -> int { i = i + 1; ret i; };
    log(error, ctr());
    log(error, ctr());
    log(error, ctr());
    log(error, ctr());
    log(error, ctr());
    log(error, i);
}
Make resolve recognize upvars Upvars are now marked with def_upvar throughout, not just when going through freevars::lookup_def. This makes things less error-prone. One thing to watch out for is that def_upvar is used in `for each` bodies too, when they refer to a local outside the body. 2011-09-01 07:35:00 -05:00			`// error-pattern:assigning to upvar`
Remove proto_sugar and 'lambda' as keyword, commit to fn@. 2012-01-09 18:12:37 -06:00			`// Make sure we can't write to upvars from fn@s`
Prohibit assignment to upvars in lambdas. Closes #805. 2011-08-04 21:31:47 -05:00			`fn main() {`
			`let i = 0;`
Remove proto_sugar and 'lambda' as keyword, commit to fn@. 2012-01-09 18:12:37 -06:00			`let ctr = fn@ () -> int { i = i + 1; ret i; };`
Register new snapshots, purge log_err and log_full in favour of log(...). 2011-12-22 19:53:53 -06:00			`log(error, ctr());`
			`log(error, ctr());`
			`log(error, ctr());`
			`log(error, ctr());`
			`log(error, ctr());`
			`log(error, i);`
Prohibit assignment to upvars in lambdas. Closes #805. 2011-08-04 21:31:47 -05:00			`}`