Exportable macros require hardcoding crate's name

[huonw]

which means the user has to import it under that name to use the macros.

// some_crate.rs
#[feature(macro_rules)];

pub static X: uint = 1;

#[macro_export]
macro_rules! foo { () => { some_crate::X } }

// other_crate.rs
#[feature(phases)];
#[phase(syntax, link)] extern mod blah = "some_crate";

fn main() { foo!(); } // unresolved name some_crate

[sfackler]

The solution I've been using is to document that certain things have to be imported from the crate when a macro is used. A better solution would be nice, but would probably require a lot of infrastructure.

[huonw]

I guess that works too, but it also requires that those things are imported under some specific name.

[huonw]

cc @kmcallister, #17103

[kmcallister]

Yeah, $crate would fix this.

[jonas-schievink]

This looks pretty fixed now

[sfackler]

Yep, has been fixed for a while.