rust/tests/ui/nll/mir_check_cast_closure.stderr

error: lifetime may not live long enough
  --> $DIR/mir_check_cast_closure.rs:5:5
   |
LL | fn bar<'a, 'b>() -> fn(&'a u32, &'b u32) -> &'a u32 {
   |        --  -- lifetime `'b` defined here
   |        |
   |        lifetime `'a` defined here
LL |     let g: fn(_, _) -> _ = |_x, y| y;
LL |     g
   |     ^ function was supposed to return data with lifetime `'a` but it is returning data with lifetime `'b`
   |
   = help: consider adding the following bound: `'b: 'a`

error: aborting due to previous error
Update tests 2018-12-11 15:49:40 -06:00			`error: lifetime may not live long enough`
Fully stabilize NLL 2022-04-01 12:13:25 -05:00			`--> $DIR/mir_check_cast_closure.rs:5:5`
move mir_check_* to ui tests, add adjusted references 2018-07-26 00:21:35 -05:00			`\|`
Explicitly label any named lifetimes mentioned in error messages. 2018-08-02 05:00:15 -05:00			`LL \| fn bar<'a, 'b>() -> fn(&'a u32, &'b u32) -> &'a u32 {`
			\| -- -- lifetime `'b` defined here
			`\| \|`
			\| lifetime `'a` defined here
move mir_check_* to ui tests, add adjusted references 2018-07-26 00:21:35 -05:00			`LL \| let g: fn(_, _) -> _ = \|_x, y\| y;`
Update tests 2018-08-07 15:48:50 -05:00			`LL \| g`
Ensure that early-bound function lifetimes are always 'local' During borrowchecking, we treat any free (early-bound) regions on the 'defining type' as `RegionClassification::External`. According to the doc comments, we should only have 'external' regions when checking a closure/generator. However, a plain function can also have some if its regions be considered 'early bound' - this occurs when the region is constrained by an argument, appears in a `where` clause, or in an opaque type. This was causing us to incorrectly mark these regions as 'external', which caused some diagnostic code to act as if we were referring to a 'parent' region from inside a closure. This PR marks all instantiated region variables as 'local' when we're borrow-checking something other than a closure/generator/inline-const. 2021-12-31 15:55:34 -06:00			\| ^ function was supposed to return data with lifetime `'a` but it is returning data with lifetime `'b`
implement outlive suggestions 2018-11-28 15:05:36 -06:00			`\|`
update tests 2019-10-27 09:39:14 -05:00			= help: consider adding the following bound: `'b: 'a`
implement outlive suggestions 2018-11-28 15:05:36 -06:00
move mir_check_* to ui tests, add adjusted references 2018-07-26 00:21:35 -05:00			`error: aborting due to previous error`