os-rust/tests/ui/imports/import-prefix-macro-2.stderr

error: expected identifier, found `a::b::c`
  --> $DIR/import-prefix-macro-2.rs:11:26
   |
LL |     ($p: path) => (use ::$p {S, Z});
   |                          ^^ expected identifier
...
LL | import! { a::b::c }
   | ------------------- in this macro invocation
   |
   = note: this error originates in the macro `import` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 1 previous error
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			error: expected identifier, found `a::b::c`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/import-prefix-macro-2.rs:11:26`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| ($p: path) => (use ::$p {S, Z});`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`\| ^^ expected identifier`
			`...`
			`LL \| import! { a::b::c }`
			`\| ------------------- in this macro invocation`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 15:56:47 +02: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 14:52:25 -05:00			= note: this error originates in the macro `import` (in Nightly builds, run with -Z macro-backtrace for more info)
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00