rust/tests/ui/imports/import-prefix-macro-1.stderr

error: expected one of `::`, `;`, or `as`, found `{`
  --> $DIR/import-prefix-macro-1.rs:11:27
   |
LL |     ($p: path) => (use $p {S, Z});
   |                           ^ expected one of `::`, `;`, or `as`
...
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 previous error
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			error: expected one of `::`, `;`, or `as`, found `{`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/import-prefix-macro-1.rs:11:27`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| ($p: path) => (use $p {S, Z});`
preserve delim spans during `macro_rules!` expansion if able 2023-01-15 10:49:34 -06:00			\| ^ expected one of `::`, `;`, or `as`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`...`
			`LL \| import! { a::b::c }`
			`\| ------------------- in this macro invocation`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 07:56:47 -06: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 `import` (in Nightly builds, run with -Z macro-backtrace for more info)
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			`error: aborting due to previous error`