rust/tests/ui/issues/issue-17758.stderr

error: lifetime may not live long enough
  --> $DIR/issue-17758.rs:7:9
   |
LL | trait Foo<'a> {
   |           -- lifetime `'a` defined here
LL |     fn foo(&'a self);
LL |     fn bar(&self) {
   |            - let's call the lifetime of this reference `'1`
LL |         self.foo();
   |         ^^^^^^^^^^ argument requires that `'1` must outlive `'a`

error: aborting due to previous error
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			`error: lifetime may not live long enough`
Fully stabilize NLL 2022-04-01 12:13:25 -05:00			`--> $DIR/issue-17758.rs:7:9`
Change compare mode to use -Zborrowck=mir 2019-01-27 05:03:21 -06:00			`\|`
Note specific regions involved in 'borrowed data escapes' error Fixes #67007 Currently, a 'borrowed data escapes' error does not mention the specific lifetime involved (except indirectly through a suggestion about adding a lifetime bound). We now explain the specific lifetime relationship that failed to hold, which improves otherwise vague error messages. 2021-10-03 15:25:26 -05:00			`LL \| trait Foo<'a> {`
			\| -- lifetime `'a` defined here
			`LL \| fn foo(&'a self);`
Change compare mode to use -Zborrowck=mir 2019-01-27 05:03:21 -06:00			`LL \| fn bar(&self) {`
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			\| - let's call the lifetime of this reference `'1`
Change compare mode to use -Zborrowck=mir 2019-01-27 05:03:21 -06:00			`LL \| self.foo();`
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			\| ^^^^^^^^^^ argument requires that `'1` must outlive `'a`
Change compare mode to use -Zborrowck=mir 2019-01-27 05:03:21 -06:00
			`error: aborting due to previous error`