rust/tests/ui/macros/derive-in-eager-expansion-hang.stderr

error: format argument must be a string literal
  --> $DIR/derive-in-eager-expansion-hang.rs:4:5
   |
LL | /     {
LL | |         #[derive(Clone)]
LL | |         struct S;
...  |
LL | |     }
   | |_____^
...
LL |       format_args!(hang!());
   |                    ------- in this macro invocation
   |
   = note: this error originates in the macro `hang` (in Nightly builds, run with -Z macro-backtrace for more info)
help: you might be missing a string literal to format with
   |
LL |     format_args!("{}", hang!());
   |                  +++++

error: aborting due to 1 previous error
Add a regression test for #44692 Add a test for the issue resolved by removing `resolve_macro_path` Add a test making sure that extern prelude entries introduced from an opaque macro are not visible anywhere, even it that macro Fix test output after rebase 2019-07-08 13:58:42 -05:00			`error: format argument must be a string literal`
			`--> $DIR/derive-in-eager-expansion-hang.rs:4:5`
			`\|`
			`LL \| / {`
			`LL \| \| #[derive(Clone)]`
			`LL \| \| struct S;`
When displaying multispans, ignore empty lines adjacent to `...` ``` error[E0308]: `match` arms have incompatible types --> tests/ui/codemap_tests/huge_multispan_highlight.rs:98:18 \| 6 \| let _ = match true { \| ---------- `match` arms have incompatible types 7 \| true => ( \| _________________- 8 \| \| // last line shown in multispan header ... \| 96 \| \| 97 \| \| ), \| \|_________- this is found to be of type `()` 98 \| false => " \| __________________^ ... \| 119 \| \| 120 \| \| ", \| \|_________^ expected `()`, found `&str` error[E0308]: `match` arms have incompatible types --> tests/ui/codemap_tests/huge_multispan_highlight.rs:215:18 \| 122 \| let _ = match true { \| ---------- `match` arms have incompatible types 123 \| true => ( \| _________________- 124 \| \| 125 \| \| 1 // last line shown in multispan header ... \| 213 \| \| 214 \| \| ), \| \|_________- this is found to be of type `{integer}` 215 \| false => " \| __________________^ 216 \| \| 217 \| \| 218 \| \| 1 last line shown in multispan ... \| 237 \| \| 238 \| \| ", \| \|_________^ expected integer, found `&str` ``` 2024-03-05 10:24:30 -06:00			`... \|`
Add a regression test for #44692 Add a test for the issue resolved by removing `resolve_macro_path` Add a test making sure that extern prelude entries introduced from an opaque macro are not visible anywhere, even it that macro Fix test output after rebase 2019-07-08 13:58:42 -05:00			`LL \| \| }`
			`\| \|_____^`
expand: Keep the correct current expansion ID for eager expansions Solve the problem of `ParentScope` entries for eager expansions not exising in the resolver map by creating them on demand. 2019-08-19 15:35:25 -05:00			`...`
			`LL \| format_args!(hang!());`
			`\| ------- in this macro invocation`
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages. 2019-10-24 00:20:58 -05:00			`\|`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 13:52:25 -06:00			= note: this error originates in the macro `hang` (in Nightly builds, run with -Z macro-backtrace for more info)
Add a regression test for #44692 Add a test for the issue resolved by removing `resolve_macro_path` Add a test making sure that extern prelude entries introduced from an opaque macro are not visible anywhere, even it that macro Fix test output after rebase 2019-07-08 13:58:42 -05:00			`help: you might be missing a string literal to format with`
			`\|`
			`LL \| format_args!("{}", hang!());`
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			`\| +++++`
Add a regression test for #44692 Add a test for the issue resolved by removing `resolve_macro_path` Add a test making sure that extern prelude entries introduced from an opaque macro are not visible anywhere, even it that macro Fix test output after rebase 2019-07-08 13:58:42 -05:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Add a regression test for #44692 Add a test for the issue resolved by removing `resolve_macro_path` Add a test making sure that extern prelude entries introduced from an opaque macro are not visible anywhere, even it that macro Fix test output after rebase 2019-07-08 13:58:42 -05:00