rust/src/test/ui/issues/issue-16683.stderr

error[E0495]: cannot infer an appropriate lifetime for autoref due to conflicting requirements
  --> $DIR/issue-16683.rs:4:14
   |
LL |         self.a();
   |              ^
   |
note: first, the lifetime cannot outlive the anonymous lifetime defined here...
  --> $DIR/issue-16683.rs:3:10
   |
LL |     fn b(&self) {
   |          ^^^^^
note: ...so that reference does not outlive borrowed content
  --> $DIR/issue-16683.rs:4:9
   |
LL |         self.a();
   |         ^^^^
note: but, the lifetime must be valid for the lifetime `'a` as defined here...
  --> $DIR/issue-16683.rs:1:9
   |
LL | trait T<'a> {
   |         ^^
note: ...so that the types are compatible
  --> $DIR/issue-16683.rs:4:14
   |
LL |         self.a();
   |              ^
   = note: expected `&'a Self`
              found `&Self`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0495`.
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`error[E0495]: cannot infer an appropriate lifetime for autoref due to conflicting requirements`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-16683.rs:4:14`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| self.a();`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\| ^`
			`\|`
Remove textual span from diagnostic string 2021-10-05 07:11:51 -05:00			`note: first, the lifetime cannot outlive the anonymous lifetime defined here...`
Update test cases 2021-02-22 08:39:06 -06:00			`--> $DIR/issue-16683.rs:3:10`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\|`
Use smaller def span for functions Currently, the def span of a funtion encompasses the entire function signature and body. However, this is usually unnecessarily verbose - when we are pointing at an entire function in a diagnostic, we almost always want to point at the signature. The actual contents of the body tends to be irrelevant to the diagnostic we are emitting, and just takes up additional screen space. This commit changes the `def_span` of all function items (freestanding functions, `impl`-block methods, and `trait`-block methods) to be the span of the signature. For example, the function ```rust pub fn foo<T>(val: T) -> T { val } ``` now has a `def_span` corresponding to `pub fn foo<T>(val: T) -> T` (everything before the opening curly brace). Trait methods without a body have a `def_span` which includes the trailing semicolon. For example: ```rust trait Foo { fn bar(); }``` the function definition `Foo::bar` has a `def_span` of `fn bar();` This makes our diagnostic output much shorter, and emphasizes information that is relevant to whatever diagnostic we are reporting. We continue to use the full span (including the body) in a few of places: * MIR building uses the full span when building source scopes. * 'Outlives suggestions' use the full span to sort the diagnostics being emitted. * The `#[rustc_on_unimplemented(enclosing_scope="in this scope")]` attribute points the entire scope body. * The 'unconditional recursion' lint uses the full span to show additional context for the recursive call. All of these cases work only with local items, so we don't need to add anything extra to crate metadata. 2020-08-12 16:02:14 -05:00			`LL \| fn b(&self) {`
Update test cases 2021-02-22 08:39:06 -06:00			`\| ^^^^^`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`note: ...so that reference does not outlive borrowed content`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-16683.rs:4:9`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| self.a();`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\| ^^^^`
Remove textual span from diagnostic string 2021-10-05 07:11:51 -05:00			note: but, the lifetime must be valid for the lifetime `'a` as defined here...
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-16683.rs:1:9`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\|`
			`LL \| trait T<'a> {`
			`\| ^^`
Include a span in more `expected...found` notes In most places, we use a span when emitting `expected...found` errors. However, there were a couple of places where we didn't use any span, resulting in hard-to-interpret error messages. This commit attaches the relevant span to these notes, and additionally switches over to using `note_expected_found` instead of manually formatting the message 2019-12-03 21:20:05 -06:00			`note: ...so that the types are compatible`
			`--> $DIR/issue-16683.rs:4:14`
			`\|`
			`LL \| self.a();`
			`\| ^`
Fix spacing of expected/found notes without a label 2019-12-19 21:44:06 -06:00			= note: expected `&'a Self`
Tweak output for mismatched impl item Detect type parameter that might require lifetime constraint. Do not name `ReVar`s in expected/found output. Reword text suggesting to check the lifetimes. 2019-12-22 15:53:01 -06:00			found `&Self`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00
			`error: aborting due to previous error`

update ui tests 2019-09-12 08:00:44 -05:00			For more information about this error, try `rustc --explain E0495`.