rust/tests/ui/did_you_mean/issue-40006.stderr

error: expected one of `!` or `::`, found `}`
  --> $DIR/issue-40006.rs:3:1
   |
LL | impl dyn A {
   |            - while parsing this item list starting here
LL |     Y
   |      - expected one of `!` or `::`
LL | }
   | ^
   | |
   | unexpected token
   | the item list ends here

error: expected one of `!` or `::`, found `(`
  --> $DIR/issue-40006.rs:8:6
   |
LL | trait X {
   |         - while parsing this item list starting here
LL |     X() {}
   |      ^ expected one of `!` or `::`
...
LL | }
   | - the item list ends here

error: expected one of `!` or `::`, found `(`
  --> $DIR/issue-40006.rs:16:6
   |
LL | trait A {
   |         - while parsing this item list starting here
LL |     X() {}
   |      ^ expected one of `!` or `::`
LL | }
   | - the item list ends here

error: expected one of `!` or `[`, found `#`
  --> $DIR/issue-40006.rs:19:17
   |
LL |     fn xxx() { ### }
   |                 ^ expected one of `!` or `[`

error: expected one of `!` or `::`, found `=`
  --> $DIR/issue-40006.rs:22:7
   |
LL | trait C {
   |         - while parsing this item list starting here
LL |     L = M;
   |       ^ expected one of `!` or `::`
LL | }
   | - the item list ends here

error: expected one of `!` or `::`, found `=`
  --> $DIR/issue-40006.rs:25:7
   |
LL | trait D {
   |         - while parsing this item list starting here
LL |     Z = { 2 + 3 };
   |       ^ expected one of `!` or `::`
LL | }
   | - the item list ends here

error: expected one of `!` or `::`, found `(`
  --> $DIR/issue-40006.rs:28:9
   |
LL | trait E {
   |         - while parsing this item list starting here
LL |     ::Y ();
   |         ^ expected one of `!` or `::`
LL | }
   | - the item list ends here

error: missing `fn` for method definition
  --> $DIR/issue-40006.rs:32:8
   |
LL | impl S {
   |        - while parsing this item list starting here
LL |     pub hello_method(&self) {
   |        ^
...
LL | }
   | - the item list ends here
   |
help: add `fn` here to parse `hello_method` as a public method
   |
LL |     pub fn hello_method(&self) {
   |         ++

error[E0599]: no method named `hello_method` found for struct `S` in the current scope
  --> $DIR/issue-40006.rs:38:7
   |
LL | struct S;
   | -------- method `hello_method` not found for this struct
...
LL |     S.hello_method();
   |       ^^^^^^^^^^^^ method not found in `S`

error: aborting due to 9 previous errors

For more information about this error, try `rustc --explain E0599`.
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			error: expected one of `!` or `::`, found `}`
			`--> $DIR/issue-40006.rs:3:1`
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-25 01:00:21 -05:00			`\|`
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			`LL \| impl dyn A {`
			`\| - while parsing this item list starting here`
			`LL \| Y`
			\| - expected one of `!` or `::`
			`LL \| }`
			`\| ^`
			`\| \|`
			`\| unexpected token`
			`\| the item list ends here`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239. 2017-04-13 14:37:05 -05:00
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			error: expected one of `!` or `::`, found `(`
			`--> $DIR/issue-40006.rs:8:6`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239. 2017-04-13 14:37:05 -05:00			`\|`
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			`LL \| trait X {`
			`\| - while parsing this item list starting here`
			`LL \| X() {}`
			\| ^ expected one of `!` or `::`
			`...`
			`LL \| }`
			`\| - the item list ends here`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239. 2017-04-13 14:37:05 -05:00
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			error: expected one of `!` or `::`, found `(`
			`--> $DIR/issue-40006.rs:16:6`
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 20:30:02 -05:00			`\|`
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			`LL \| trait A {`
			`\| - while parsing this item list starting here`
			`LL \| X() {}`
			\| ^ expected one of `!` or `::`
			`LL \| }`
			`\| - the item list ends here`
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 20:30:02 -05:00
unify/improve/simplify attribute parsing 2020-03-05 04:42:56 -06: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 20:30:02 -05:00			`--> $DIR/issue-40006.rs:19:17`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239. 2017-04-13 14:37:05 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| fn xxx() { ### }`
unify/improve/simplify attribute parsing 2020-03-05 04:42:56 -06:00			\| ^ expected one of `!` or `[`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239. 2017-04-13 14:37:05 -05:00
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			error: expected one of `!` or `::`, found `=`
			`--> $DIR/issue-40006.rs:22:7`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239. 2017-04-13 14:37:05 -05:00			`\|`
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			`LL \| trait C {`
			`\| - while parsing this item list starting here`
			`LL \| L = M;`
			\| ^ expected one of `!` or `::`
			`LL \| }`
			`\| - the item list ends here`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239. 2017-04-13 14:37:05 -05:00
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			error: expected one of `!` or `::`, found `=`
			`--> $DIR/issue-40006.rs:25:7`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239. 2017-04-13 14:37:05 -05:00			`\|`
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			`LL \| trait D {`
			`\| - while parsing this item list starting here`
			`LL \| Z = { 2 + 3 };`
			\| ^ expected one of `!` or `::`
			`LL \| }`
			`\| - the item list ends here`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239. 2017-04-13 14:37:05 -05: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 20:30:02 -05:00			`--> $DIR/issue-40006.rs:28:9`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239. 2017-04-13 14:37:05 -05:00			`\|`
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			`LL \| trait E {`
			`\| - while parsing this item list starting here`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| ::Y ();`
Remove "here" from "expected one of X here" 2019-10-28 13:08:53 -05:00			\| ^ expected one of `!` or `::`
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			`LL \| }`
			`\| - the item list ends here`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239. 2017-04-13 14:37:05 -05:00
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			error: missing `fn` for method definition
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 20:30:02 -05:00			`--> $DIR/issue-40006.rs:32:8`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239. 2017-04-13 14:37:05 -05:00			`\|`
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			`LL \| impl S {`
			`\| - while parsing this item list starting here`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| pub hello_method(&self) {`
parse: use `parse_item_common` in `parse_assoc_item_`. 2020-02-22 01:16:39 -06:00			`\| ^`
			`...`
			`LL \| }`
			`\| - the item list ends here`
			`\|`
			help: add `fn` here to parse `hello_method` as a public method
			`\|`
			`LL \| pub fn hello_method(&self) {`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`\| ++`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239. 2017-04-13 14:37:05 -05:00
Unify output of "variant not found" errors 2020-01-08 10:05:31 -06:00			error[E0599]: no method named `hello_method` found for struct `S` in the current scope
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 20:30:02 -05:00			`--> $DIR/issue-40006.rs:38:7`
libsyntax/parse: improve associated item error reporting Fixes #41161. Fixes #41239. 2017-04-13 14:37:05 -05: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 20:30:02 -05:00			`LL \| struct S;`
Track implicit `Sized` obligations in type params Suggest adding a `?Sized` bound if appropriate on E0599 by inspecting the HIR Generics. (Fix #98539) 2022-07-01 18:47:26 -05:00			\| -------- method `hello_method` not found for this struct
On object safety violation, point at source when possible 2019-09-02 22:22:22 -05: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 20:30:02 -05: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-25 01:00:21 -05: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 08:09:09 -05: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-25 01:00:21 -05: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 20:30:02 -05:00			For more information about this error, try `rustc --explain E0599`.