rust/tests/ui/borrowck/borrowck-move-by-capture.rs

#![feature(unboxed_closures, tuple_trait)]

fn to_fn_mut<A:std::marker::Tuple,F:FnMut<A>>(f: F) -> F { f }
fn to_fn_once<A:std::marker::Tuple,F:FnOnce<A>>(f: F) -> F { f }

pub fn main() {
    let bar: Box<_> = Box::new(3);
    let _g = to_fn_mut(|| {
        let _h = to_fn_once(move || -> isize { *bar }); //~ ERROR cannot move out of
    });
}
Adjust diagnostics, bless tests 2022-07-30 05:37:48 +00:00			`#![feature(unboxed_closures, tuple_trait)]`
Update compile-fail tests to use the expected type to force the closure kind, thereby detecting what happens if there are mismatches. Simply removing the `:` annotations caused most of these tests to pass or produce other errors, because the inference would convert the closure into a more appropriate kind. (The ability to override the inference by using the expected type is an important backdoor partly for this reason.) 2015-02-03 11:32:26 -05:00
Adjust diagnostics, bless tests 2022-07-30 05:37:48 +00:00			`fn to_fn_mut<A:std::marker::Tuple,F:FnMut<A>>(f: F) -> F { f }`
			`fn to_fn_once<A:std::marker::Tuple,F:FnOnce<A>>(f: F) -> F { f }`
Test fixes and rebase conflicts 2015-01-07 18:53:58 -08:00
Defer reasoning about region relationships until after regionck. This patch makes error handling for region inference failures more uniform by not reporting any region errors until the reigon inference step. This requires threading through more information about what caused a region constraint, so that we can still give informative error messages. I have only taken partial advantage of this information: when region inference fails, we still report the same error we always did, despite the fact that we now know precisely what caused the various constriants and what the region variable represents, which we did not know before. This change is required not only to improve error messages but because the region hierarchy is not in fact fully known until regionck, because it is not clear where closure bodies fit in (our current treatment is unsound). Moreover, the relationships between free variables cannot be fully determined until type inference is otherwise complete. cc #3238. 2013-05-23 21:37:37 -04:00			`pub fn main() {`
Remove box syntax from most places in src/test outside of the issues dir 2021-08-25 02:39:40 +02:00			`let bar: Box<_> = Box::new(3);`
Update compile-fail tests to use the expected type to force the closure kind, thereby detecting what happens if there are mismatches. Simply removing the `:` annotations caused most of these tests to pass or produce other errors, because the inference would convert the closure into a more appropriate kind. (The ability to override the inference by using the expected type is an important backdoor partly for this reason.) 2015-02-03 11:32:26 -05:00			`let _g = to_fn_mut(\|\| {`
			`let _h = to_fn_once(move \|\| -> isize { *bar }); //~ ERROR cannot move out of`
			`});`
Finalize moves-based-on-type implementation. Changes: - Refactor move mode computation - Removes move mode arguments, unary move, capture clauses (though they still parse for backwards compatibility) - Simplify how moves are handled in trans - Fix a number of illegal copies that cropped up - Workaround for bug involving def-ids in params (see details below) Future work (I'll open bugs for these...): - Improve error messages for moves that are due to bindings - Add support for moving owned content like a.b.c to borrow check, test in trans (but I think it'll "just work") - Proper fix for def-ids in params Def ids in params: Move captures into a map instead of recomputing. This is a workaround for a larger bug having to do with the def-ids associated with ty_params, which are not always properly preserved when inlining. I am not sure of my preferred fix for the larger bug yet. This current fix removes the only code in trans that I know of which relies on ty_param def-ids, but feels fragile. 2013-01-10 10:59:58 -08:00			`}`