rust/tests/ui/nll/issue-55394.stderr

error: lifetime may not live long enough
  --> $DIR/issue-55394.rs:9:9
   |
LL |     fn new(bar: &mut Bar) -> Self {
   |                 -            ---- return type is Foo<'2>
   |                 |
   |                 let's call the lifetime of this reference `'1`
LL |         Foo { bar }
   |         ^^^^^^^^^^^ associated function was supposed to return data with lifetime `'2` but it is returning data with lifetime `'1`

error: aborting due to 1 previous error
Remove feature(nll) when compare mode is sufficient 2019-04-07 15:07:36 +00:00			`error: lifetime may not live long enough`
Fully stabilize NLL 2022-04-01 17:13:25 +00:00			`--> $DIR/issue-55394.rs:9:9`
Remove feature(nll) when compare mode is sufficient 2019-04-07 15:07:36 +00:00			`\|`
			`LL \| fn new(bar: &mut Bar) -> Self {`
			`\| - ---- return type is Foo<'2>`
			`\| \|`
			\| let's call the lifetime of this reference `'1`
			`LL \| Foo { bar }`
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			\| ^^^^^^^^^^^ associated function was supposed to return data with lifetime `'2` but it is returning data with lifetime `'1`
Remove feature(nll) when compare mode is sufficient 2019-04-07 15:07:36 +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`
Remove feature(nll) when compare mode is sufficient 2019-04-07 15:07:36 +00:00