-
Notifications
You must be signed in to change notification settings - Fork 13.3k
quote_expr!() can cause early abort #14282
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
Comments
@kballard could you include a small reproduction snippet to help make this issue more concrete? |
@tamird I filed this issue almost a year ago. I don't recall the circumstances surrounding it, beyond what I put in the ticket. From re-reading this, I'm pretty sure that what I was saying is that if a syntax extension uses |
Triage: this ticket hasn't had an update in almost two years, and there's no reproduction. As such, I'm going to give it a close. If someone runs into this today and can reproduce, please let me know! |
…eykril fix: Load proc-macros for rustc_private crates Fixes rust-lang/rust-analyzer#13591 Verified that this makes things work in the clippy repo (like resolving `sym` things for example)
r? flip1995 changelog: none
It seems as though using
quote_expr!()
in a syntax extension after aspan_err()
will cause rustc to abort early instead of finishing the macro expansion phase.I hit this in my
bytes!()
PR, where I ended up having to track whether I had an error and useDummyResult
instead ofquote_expr!()
.The text was updated successfully, but these errors were encountered: