-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macros: Improve tt
matchers
#34908
macros: Improve tt
matchers
#34908
Conversation
Looks like this breaks some non-trivial macro-expanded This should be able to land without breakage once I fix non-trivial macro-expanded |
cc @eddyb |
LGTM, pending on #34925 landing. |
ddf7ae9
to
082970c
Compare
This is ready to land now pending review (cc @nrc). |
@bors: r+ |
📌 Commit 082970c has been approved by |
⌛ Testing commit 082970c with merge ee0dc3a... |
💔 Test failed - auto-win-msvc-64-opt |
@bors retry |
⌛ Testing commit 082970c with merge bb5f00b... |
💔 Test failed - auto-win-msvc-64-opt-rustbuild |
@bors: retry On Tue, Jul 26, 2016 at 3:24 AM, bors notifications@github.com wrote:
|
⌛ Testing commit 082970c with merge d69a893... |
💔 Test failed - auto-win-gnu-32-opt-rustbuild |
082970c
to
4485502
Compare
@bors r=nrc |
📌 Commit 4485502 has been approved by |
⌛ Testing commit 4485502 with merge 4e0fcad... |
@bors: retry force clean
|
Has this innocuously named PR finally killed the reparse hack? https://is.gd/tV0iba macro_rules! as_item { ($i:item) => { $i } }
macro_rules! foo {
($x:tt) => {
//as_item!{ // uncomment for stable
struct Item($x);
//}
}
}
foo!(i32);
fn main() {} |
@durka That's what was fixed here, yeah. |
That makes me unjustifiably happy. Please tag this with |
Rust 1.11 had an old behaviour for `tt` matchers that has been fixed in Rust 1.12 (rust-lang/rust#34908).
Fixes #5846, fixes #22819.
r? @nrc