mathieu/os-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
os-rust/src/test/ui/did_you_mean/issue-40006.stderr

71 lines
1.8 KiB
Text
Raw Normal View History

libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
error: missing `fn`, `type`, or `const` for impl-item declaration
Update ui test suite to use dyn
2019-05-28 14:46:13 -04:00
--> $DIR/issue-40006.rs:1:13
Identify missing item category in `impl`s ```rust struct S; impl S { pub hello_method(&self) { println!("Hello"); } } fn main() { S.hello_method(); } ``` ```rust error: can't qualify macro invocation with `pub` --> file.rs:3:4 | 3 | pub hello_method(&self) { | ^^^- - expected `!` here for a macro invocation | | | did you mean to write `fn` here for a method declaration? | = help: try adjusting the macro to put `pub` inside the invocation ```
2017-03-24 23:00:21 -07:00
|
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-25 18:30:02 -07:00
LL | impl dyn A {
Update ui test suite to use dyn
2019-05-28 14:46:13 -04:00
| _____________^
Update UI tests
2018-02-23 03:42:32 +03:00
LL | | Y
Reduce visual clutter of multiline start when possible When a span starts on a line with nothing but whitespace to the left, and there are no other annotations in that line, simplify the visual representation of the span. Go from: ```rust error[E0072]: recursive type `A` has infinite size --> file2.rs:1:1 | 1 | struct A { | _^ starting here... 2 | | a: A, 3 | | } | |_^ ...ending here: recursive type has infinite size | ``` To: ```rust error[E0072]: recursive type `A` has infinite size --> file2.rs:1:1 | 1 | / struct A { 2 | | a: A, 3 | | } | |_^ recursive type has infinite size ``` Remove `starting here...`/`...ending here` labels from all multiline diagnostics.
2017-04-14 16:38:10 -07:00
| |____^ missing `fn`, `type`, or `const`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
error: missing `fn`, `type`, or `const` for trait-item declaration
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-25 18:30:02 -07:00
--> $DIR/issue-40006.rs:7:10
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
|
Update tests
2019-03-09 15:03:44 +03:00
LL | trait X {
Reduce visual clutter of multiline start when possible When a span starts on a line with nothing but whitespace to the left, and there are no other annotations in that line, simplify the visual representation of the span. Go from: ```rust error[E0072]: recursive type `A` has infinite size --> file2.rs:1:1 | 1 | struct A { | _^ starting here... 2 | | a: A, 3 | | } | |_^ ...ending here: recursive type has infinite size | ``` To: ```rust error[E0072]: recursive type `A` has infinite size --> file2.rs:1:1 | 1 | / struct A { 2 | | a: A, 3 | | } | |_^ recursive type has infinite size ``` Remove `starting here...`/`...ending here` labels from all multiline diagnostics.
2017-04-14 16:38:10 -07:00
| __________^
Update UI tests
2018-02-23 03:42:32 +03:00
LL | | X() {}
Reduce visual clutter of multiline start when possible When a span starts on a line with nothing but whitespace to the left, and there are no other annotations in that line, simplify the visual representation of the span. Go from: ```rust error[E0072]: recursive type `A` has infinite size --> file2.rs:1:1 | 1 | struct A { | _^ starting here... 2 | | a: A, 3 | | } | |_^ ...ending here: recursive type has infinite size | ``` To: ```rust error[E0072]: recursive type `A` has infinite size --> file2.rs:1:1 | 1 | / struct A { 2 | | a: A, 3 | | } | |_^ recursive type has infinite size ``` Remove `starting here...`/`...ending here` labels from all multiline diagnostics.
2017-04-14 16:38:10 -07:00
| |____^ missing `fn`, `type`, or `const`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-25 18:30:02 -07:00
error: missing `fn`, `type`, or `const` for trait-item declaration
--> $DIR/issue-40006.rs:15:10
|
LL | trait A {
| __________^
LL | | X() {}
| |____^ missing `fn`, `type`, or `const`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
error: expected `[`, found `#`
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-25 18:30:02 -07:00
--> $DIR/issue-40006.rs:19:17
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
|
Update tests
2019-03-09 15:03:44 +03:00
LL | fn xxx() { ### }
Detect missing `if` blocks When unnecessarily using a fat arrow after an if condition, suggest the removal of it. When finding an if statement with no block, point at the `if` keyword to provide more context.
2018-02-18 16:59:33 -08:00
| ^ expected `[`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
error: missing `fn`, `type`, or `const` for trait-item declaration
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-25 18:30:02 -07:00
--> $DIR/issue-40006.rs:21:10
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
|
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-25 18:30:02 -07:00
LL | trait C {
| __________^
Update tests
2019-03-09 15:03:44 +03:00
LL | | L = M;
Reduce visual clutter of multiline start when possible When a span starts on a line with nothing but whitespace to the left, and there are no other annotations in that line, simplify the visual representation of the span. Go from: ```rust error[E0072]: recursive type `A` has infinite size --> file2.rs:1:1 | 1 | struct A { | _^ starting here... 2 | | a: A, 3 | | } | |_^ ...ending here: recursive type has infinite size | ``` To: ```rust error[E0072]: recursive type `A` has infinite size --> file2.rs:1:1 | 1 | / struct A { 2 | | a: A, 3 | | } | |_^ recursive type has infinite size ``` Remove `starting here...`/`...ending here` labels from all multiline diagnostics.
2017-04-14 16:38:10 -07:00
| |____^ missing `fn`, `type`, or `const`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
error: missing `fn`, `type`, or `const` for trait-item declaration
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-25 18:30:02 -07:00
--> $DIR/issue-40006.rs:24:10
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
|
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-25 18:30:02 -07:00
LL | trait D {
| __________^
Update tests
2019-03-09 15:03:44 +03:00
LL | | Z = { 2 + 3 };
Reduce visual clutter of multiline start when possible When a span starts on a line with nothing but whitespace to the left, and there are no other annotations in that line, simplify the visual representation of the span. Go from: ```rust error[E0072]: recursive type `A` has infinite size --> file2.rs:1:1 | 1 | struct A { | _^ starting here... 2 | | a: A, 3 | | } | |_^ ...ending here: recursive type has infinite size | ``` To: ```rust error[E0072]: recursive type `A` has infinite size --> file2.rs:1:1 | 1 | / struct A { 2 | | a: A, 3 | | } | |_^ recursive type has infinite size ``` Remove `starting here...`/`...ending here` labels from all multiline diagnostics.
2017-04-14 16:38:10 -07:00
| |____^ missing `fn`, `type`, or `const`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
error: expected one of `!` or `::`, found `(`
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-25 18:30:02 -07:00
--> $DIR/issue-40006.rs:28:9
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
|
Update tests
2019-03-09 15:03:44 +03:00
LL | ::Y ();
Point to next token when it is in the expected line
2017-11-29 13:28:47 -08:00
| ^ expected one of `!` or `::` here
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
error: missing `fn`, `type`, or `const` for impl-item declaration
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-25 18:30:02 -07:00
--> $DIR/issue-40006.rs:32:8
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
|
Update tests
2019-03-09 15:03:44 +03:00
LL | pub hello_method(&self) {
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
| ^ missing `fn`, `type`, or `const`
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-25 18:30:02 -07:00
error[E0599]: no method named `hello_method` found for type `S` in the current scope
--> $DIR/issue-40006.rs:38:7
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239.
2017-04-13 22:37:05 +03:00
|
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-25 18:30:02 -07:00
LL | struct S;
| --------- method `hello_method` not found for this
On object safety violation, point at source when possible
2019-09-02 20:22:22 -07:00
...
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-25 18:30:02 -07:00
LL | S.hello_method();
| ^^^^^^^^^^^^ method not found in `S`
Identify missing item category in `impl`s ```rust struct S; impl S { pub hello_method(&self) { println!("Hello"); } } fn main() { S.hello_method(); } ``` ```rust error: can't qualify macro invocation with `pub` --> file.rs:3:4 | 3 | pub hello_method(&self) { | ^^^- - expected `!` here for a macro invocation | | | did you mean to write `fn` here for a method declaration? | = help: try adjusting the macro to put `pub` inside the invocation ```
2017-03-24 23:00:21 -07:00
report the total number of errors on compilation failure Prior to this PR, when we aborted because a "critical pass" failed, we displayed the number of errors from that critical pass. While that's the number of errors that caused compilation to abort in *that place*, that's not what people really want to know. Instead, always report the total number of errors, and don't bother to track the number of errors from the last pass that failed. This changes the compiler driver API to handle errors more smoothly, and therefore is a compiler-api-[breaking-change]. Fixes #42793.
2017-07-02 16:09:09 +03:00
error: aborting due to 9 previous errors
Identify missing item category in `impl`s ```rust struct S; impl S { pub hello_method(&self) { println!("Hello"); } } fn main() { S.hello_method(); } ``` ```rust error: can't qualify macro invocation with `pub` --> file.rs:3:4 | 3 | pub hello_method(&self) { | ^^^- - expected `!` here for a macro invocation | | | did you mean to write `fn` here for a method declaration? | = help: try adjusting the macro to put `pub` inside the invocation ```
2017-03-24 23:00:21 -07:00
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-25 18:30:02 -07:00
For more information about this error, try `rustc --explain E0599`.
Reference in a new issue Copy permalink