You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dylan-DPC-zz opened this issue
Mar 4, 2019
· 3 comments
Labels
A-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)A-resolveArea: Name/path resolution done by `rustc_resolve` specificallyT-langRelevant to the language team, which will review and decide on the PR/issue.
use subcrate::macros::foo -> use subcrate::foo. macro_export-ed macros are placed into the crate root rather than into the module they are defined in.
AFAIR, the latter was considered during macro import stabilization, but it was too late for a breaking change that large.
jonas-schievink
added
A-resolve
Area: Name/path resolution done by `rustc_resolve` specifically
A-macros
Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
labels
Mar 4, 2019
A-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)A-resolveArea: Name/path resolution done by `rustc_resolve` specificallyT-langRelevant to the language team, which will review and decide on the PR/issue.
Setup:
You have a workspace, with one subcrate. The subcrate contains a macro (which is exported).
The main crate in the workspace uses the subcrate as a dependency, but it cannot resolve the macro by importing it with
use
(the 2018 edition way)Here is a PoC: https://github.com/Dylan-DPC/macros-workspace-test
Rust version: 1.33.0 (stable)
Edition: 2018
The text was updated successfully, but these errors were encountered: