rust-lang/rust
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
ce1a521012017a352dc15ef1036b3dc56fa676ca
rust/src/test/ui/issues/issue-17740.stderr

42 lines
1.2 KiB
Plaintext
Raw Normal View History

Refer to "`self` type" instead of "receiver type"
2019-09-02 18:21:58 -07:00
error[E0308]: mismatched `self` parameter type
Remove licenses
2018-12-25 08:56:47 -07:00
--> $DIR/issue-17740.rs:6:18
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
LL | fn bar(self: &mut Foo) {
| ^^^^^^^^ lifetime mismatch
|
Specific labels when referring to "expected" and "found" types
2019-11-13 14:16:56 -08:00
= note: expected struct `Foo<'a>`
found struct `Foo<'_>`
Remove licenses
2018-12-25 08:56:47 -07:00
note: the anonymous lifetime #2 defined on the method body at 6:5...
--> $DIR/issue-17740.rs:6:5
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07: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 17:02:14 -04:00
LL | fn bar(self: &mut Foo) {
| ^^^^^^^^^^^^^^^^^^^^^^
Print lifetimes with backticks
2019-10-11 08:58:35 +09:00
note: ...does not necessarily outlive the lifetime `'a` as defined on the impl at 5:7
Remove licenses
2018-12-25 08:56:47 -07:00
--> $DIR/issue-17740.rs:5:7
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
LL | impl <'a> Foo<'a>{
| ^^
Refer to "`self` type" instead of "receiver type"
2019-09-02 18:21:58 -07:00
error[E0308]: mismatched `self` parameter type
Remove licenses
2018-12-25 08:56:47 -07:00
--> $DIR/issue-17740.rs:6:18
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
LL | fn bar(self: &mut Foo) {
| ^^^^^^^^ lifetime mismatch
|
Specific labels when referring to "expected" and "found" types
2019-11-13 14:16:56 -08:00
= note: expected struct `Foo<'a>`
found struct `Foo<'_>`
Print lifetimes with backticks
2019-10-11 08:58:35 +09:00
note: the lifetime `'a` as defined on the impl at 5:7...
Remove licenses
2018-12-25 08:56:47 -07:00
--> $DIR/issue-17740.rs:5:7
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
LL | impl <'a> Foo<'a>{
| ^^
Remove licenses
2018-12-25 08:56:47 -07:00
note: ...does not necessarily outlive the anonymous lifetime #2 defined on the method body at 6:5
--> $DIR/issue-17740.rs:6:5
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07: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 17:02:14 -04:00
LL | fn bar(self: &mut Foo) {
| ^^^^^^^^^^^^^^^^^^^^^^
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
error: aborting due to 2 previous errors
For more information about this error, try `rustc --explain E0308`.
Reference in New Issue Copy Permalink