rust/src/test/ui/proc-macro/issue-59191-replace-root-with-fn.stderr

error: expected crate top-level item to be a module after macro expansion, found a function
  --> $DIR/issue-59191-replace-root-with-fn.rs:6:1
   |
LL | #![issue_59191::no_main]
   | ^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in the attribute macro `issue_59191::no_main` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error
Add tests for issue 59191 2020-02-01 20:07:26 -06:00			`error: expected crate top-level item to be a module after macro expansion, found a function`
Implement RFC 1260 with feature_name `imported_main`. 2021-04-25 12:09:35 -05:00			`--> $DIR/issue-59191-replace-root-with-fn.rs:6:1`
Add tests for issue 59191 2020-02-01 20:07:26 -06:00			`\|`
			`LL \| #![issue_59191::no_main]`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^`
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 attribute macro `issue_59191::no_main` (in Nightly builds, run with -Z macro-backtrace for more info)
Add tests for issue 59191 2020-02-01 20:07:26 -06:00
Implement RFC 1260 with feature_name `imported_main`. 2021-04-25 12:09:35 -05:00			`error: aborting due to previous error`
Add tests for issue 59191 2020-02-01 20:07:26 -06:00