Using the quote_tokens!() macro results in unresolved ext_cx errors

[colemickens]

This is predicated on the notion that I'm not trying to quote_tokens! horribly incorrectly.

cole@medusa ⮀ ~/Code/rustpkgs/colemickens/quote ⮀ cat quote_test.rs

extern mod std;
extern mod syntax;

fn main() {
    quote_tokens!(
        these.are_some(balling_tokens)
    )
}

cole@medusa ⮀ ~/Code/rustpkgs/colemickens/quote ⮀ rustc quote_test.rs

quote_test.rs:5:1: 1:0 error: unresolved name: `ext_cx`.
note: in expansion of quote_tokens!
quote_test.rs:5:1: 1:0 note: expansion site
quote_test.rs:6:2: 6:7 error: unresolved name: `ext_cx`. Did you mean: `tt`?
quote_test.rs:6                 these.are_some(balling_tokens)
                                ^~~~~
note: in expansion of quote_tokens!
quote_test.rs:5:1: 1:0 note: expansion site
quote_test.rs:6:8: 6:16 error: unresolved name: `ext_cx`. Did you mean: `tt`?
quote_test.rs:6                 these.are_some(balling_tokens)
                                      ^~~~~~~~
note: in expansion of quote_tokens!
quote_test.rs:5:1: 1:0 note: expansion site
quote_test.rs:6:17: 6:31 error: unresolved name: `ext_cx`. Did you mean: `tt`?
quote_test.rs:6                 these.are_some(balling_tokens)
                                               ^~~~~~~~~~~~~~
note: in expansion of quote_tokens!
quote_test.rs:5:1: 1:0 note: expansion site
error: aborting due to 4 previous errors

[metajack]

Still happens.

@jbclements is this worth nominating?

[jbclements]

No, I don't think so. I'm sorry I didn't see this one earlier. The answer is that quote_tokens is currently written in such a way that it
a) is cloaking(/unhygienic), and
b) requires an in-scope variable named ext_cx
This is very nasty, in my opinion. It's probably worth opening an issue called "rewrite quote_tokens (etc.) to not be so icky". However, this is not a bug, per se.
I'll open an issue on that, and close this one.