Importing macros: maybe mention magic-compiler-internal std macros?

[LukasKalbertodt]

I was a bit confused by the chapter about macro imports. See this StackOverflow question. In short: there are some macros in std that cannot be imported via use. Maybe this should be mentioned? Right now it sounds like I can import all macros from extern crates via use.

And/or: maybe this is a bug and it should be possible to import the macros via use, too?

[steveklabnik]

I *think* this is a bug, but I’m not sure.

…

On Mar 31, 2019, at 2:12 PM, Lukas Kalbertodt ***@***.***> wrote: I was a bit confused by the chapter about macro imports. See this StackOverflow question. In short: there are some macros in std that cannot be imported via use. Maybe this should be mentioned? Right now it sounds like I can import all macros from extern crates via use. And/or: maybe this is a bug and it should be possible to import the macros via use, too? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[LukasKalbertodt]

@steveklabnik Might very well be! @shepmaster found this thread where it's briefly mentioned.

[ehuss]

In #232 this section has moved to https://github.com/rust-lang/edition-guide/blob/302a115e8f71876dfc884aebb0ca5ccb02b8a962/src/rust-2018/path-changes.md#macros.

I have been working on name resolution documentation for the reference, and hopefully the use chapter will get updated with all sorts of goodness. And I believe since this has been written, many macros have become less magic and more "normal".

[ehuss]

I believe this is now resolved via rust-lang/rust#62086 (built-in macros can now be imported).