-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Address two regressions #53653
Address two regressions #53653
Conversation
…iven `Mark`" This reverts commit b15785b.
…port` macros into a deprecation lint
r? @cramertj (rust_highfive has picked a reviewer for you, use r? to override) |
Looks good to me code-wise, but I'm somewhat concerned about just removing the assert there -- is there something it's guarding against? @bors r+ p=1 because this unblocks html5ever perf |
📌 Commit 77f2a2f has been approved by |
Yes, it's guarding against something that shouldn't happen according to the expansion logic and is clearly a bug. |
I'll re-purpose the issue for investigating why that assert fires. |
⌛ Testing commit 77f2a2f with merge 571f45306549d154977c4d3141df66d940e7e6a7... |
💔 Test failed - status-travis |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Spurious: |
☀️ Test successful - status-appveyor, status-travis |
Accepting for beta. cc @rust-lang/compiler |
@petrochenkov while cherry-picking this into beta, I noticed the code requires some changes introduced in #53270. Should that PR also be backported? |
@pietroalbini |
Remove assert checking that expansion data is immutable until I have time to investigate why it's firing, cc #52363
Turn the error for module-relative access to macro-expanded
macro_export
macros into a deprecation lint, closes #53495