mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
d84907bbcc
rust/src/test/ui/issue-59764.stderr

31 lines
952 B
Plaintext
Raw Normal View History

Add test with current behaviour. This commit adds a test demonstrating the current behaviour when a macro defined in a module with the `#[macro_export]` is imported from the module rather than the crate root.
2019-04-07 10:56:50 -05:00
error[E0432]: unresolved import `issue_59764::foo::makro`
Suggest macro import from crate root. This commit suggests importing a macro from the root of a crate as the intent may have been to import a macro from the definition location that was annotated with `#[macro_export]`.
2019-04-07 12:56:41 -05:00
--> $DIR/issue-59764.rs:6:5
Add test with current behaviour. This commit adds a test demonstrating the current behaviour when a macro defined in a module with the `#[macro_export]` is imported from the module rather than the crate root.
2019-04-07 10:56:50 -05:00
|
LL | use issue_59764::foo::makro;
| ^^^^^^^^^^^^^^^^^^^^^^^ no `makro` in `foo`
Suggest macro import from crate root. This commit suggests importing a macro from the root of a crate as the intent may have been to import a macro from the definition location that was annotated with `#[macro_export]`.
2019-04-07 12:56:41 -05:00
|
= note: this could be because a macro annotated with `#[macro_export]` will be exported at the root of the crate instead of the module where it is defined
help: a macro with this name exists at the root of the crate
|
LL | use issue_59764::makro;
| ^^^^^^^^^^^^^^^^^^
Add test with current behaviour. This commit adds a test demonstrating the current behaviour when a macro defined in a module with the `#[macro_export]` is imported from the module rather than the crate root.
2019-04-07 10:56:50 -05:00
error: cannot determine resolution for the macro `makro`
Suggest macro import from crate root. This commit suggests importing a macro from the root of a crate as the intent may have been to import a macro from the definition location that was annotated with `#[macro_export]`.
2019-04-07 12:56:41 -05:00
--> $DIR/issue-59764.rs:9:1
Add test with current behaviour. This commit adds a test demonstrating the current behaviour when a macro defined in a module with the `#[macro_export]` is imported from the module rather than the crate root.
2019-04-07 10:56:50 -05:00
|
LL | makro!(bar);
| ^^^^^
|
= note: import resolution is stuck, try simplifying macro imports
error[E0425]: cannot find function `bar` in this scope
Suggest macro import from crate root. This commit suggests importing a macro from the root of a crate as the intent may have been to import a macro from the definition location that was annotated with `#[macro_export]`.
2019-04-07 12:56:41 -05:00
--> $DIR/issue-59764.rs:13:5
Add test with current behaviour. This commit adds a test demonstrating the current behaviour when a macro defined in a module with the `#[macro_export]` is imported from the module rather than the crate root.
2019-04-07 10:56:50 -05:00
|
LL | bar();
| ^^^ not found in this scope
error: aborting due to 3 previous errors
Some errors occurred: E0425, E0432.
For more information about an error, try `rustc --explain E0425`.
Reference in New Issue Copy Permalink