rust/tests/ui/variance/variance-use-contravariant-struct-1.stderr

error: lifetime may not live long enough
  --> $DIR/variance-use-contravariant-struct-1.rs:10:5
   |
LL | fn foo<'min,'max>(v: SomeStruct<&'max ()>)
   |        ---- ---- lifetime `'max` defined here
   |        |
   |        lifetime `'min` defined here
...
LL |     v
   |     ^ function was supposed to return data with lifetime `'max` but it is returning data with lifetime `'min`
   |
   = help: consider adding the following bound: `'min: 'max`

error: aborting due to 1 previous error
Change compare mode to use -Zborrowck=mir 2019-01-27 11:03:21 +00:00			`error: lifetime may not live long enough`
Fully stabilize NLL 2022-04-01 17:13:25 +00:00			`--> $DIR/variance-use-contravariant-struct-1.rs:10:5`
Change compare mode to use -Zborrowck=mir 2019-01-27 11:03:21 +00:00			`\|`
			`LL \| fn foo<'min,'max>(v: SomeStruct<&'max ()>)`
			\| ---- ---- lifetime `'max` defined here
			`\| \|`
			\| lifetime `'min` defined here
			`...`
			`LL \| v`
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 21:55:34 +00:00			\| ^ function was supposed to return data with lifetime `'max` but it is returning data with lifetime `'min`
update tests 2019-10-27 14:39:14 +00:00			`\|`
			= help: consider adding the following bound: `'min: 'max`
Change compare mode to use -Zborrowck=mir 2019-01-27 11:03:21 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Change compare mode to use -Zborrowck=mir 2019-01-27 11:03:21 +00:00