2017-12-10 13:47:55 -06:00
error: `macro_two` is already in scope
2018-12-25 09:56:47 -06:00
--> $DIR/macro-shadowing.rs:12:5
2017-12-10 13:47:55 -06:00
|
2019-03-09 06:03:44 -06:00
LL | #[macro_use]
2017-12-10 13:47:55 -06:00
| ^^^^^^^^^^^^
...
2018-02-22 18:42:32 -06:00
LL | m1!();
2021-10-14 13:28:28 -05:00
| ----- in this macro invocation
2017-12-10 13:47:55 -06:00
|
= note: macro-expanded `#[macro_use]`s may not shadow existing macros (see RFC 1560)
2021-02-13 13:52:25 -06:00
= note: this error originates in the macro `m1` (in Nightly builds, run with -Z macro-backtrace for more info)
2017-12-10 13:47:55 -06:00
2021-10-20 08:56:10 -05:00
error[E0659]: `foo` is ambiguous
2018-12-25 09:56:47 -06:00
--> $DIR/macro-shadowing.rs:17:1
2018-08-27 17:41:07 -05:00
|
2019-03-09 06:03:44 -06:00
LL | foo!();
2018-09-07 18:51:20 -05:00
| ^^^ ambiguous name
2018-08-27 17:41:07 -05:00
|
2021-10-20 08:56:10 -05:00
= note: ambiguous because of a conflict between a macro-expanded name and a less macro-expanded name from outer scope during import or macro resolution
2018-11-04 16:11:59 -06:00
note: `foo` could refer to the macro defined here
2018-12-25 09:56:47 -06:00
--> $DIR/macro-shadowing.rs:10:5
2017-12-10 13:47:55 -06:00
|
2018-08-27 17:41:07 -05:00
LL | macro_rules! foo { () => {} }
2017-12-10 13:47:55 -06:00
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
2018-02-22 18:42:32 -06:00
LL | m1!();
2021-10-14 13:28:28 -05:00
| ----- in this macro invocation
2018-11-04 16:11:59 -06:00
note: `foo` could also refer to the macro defined here
2018-12-25 09:56:47 -06:00
--> $DIR/macro-shadowing.rs:5:1
2017-12-10 13:47:55 -06:00
|
2018-08-27 17:41:07 -05:00
LL | macro_rules! foo { () => {} }
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2021-02-13 13:52:25 -06:00
= note: this error originates in the macro `m1` (in Nightly builds, run with -Z macro-backtrace for more info)
2017-12-10 13:47:55 -06:00
2018-08-28 19:23:28 -05:00
error: aborting due to 2 previous errors
2017-12-10 13:47:55 -06:00
2018-08-27 17:41:07 -05:00
For more information about this error, try `rustc --explain E0659`.