-
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
fix top level attr spans #36539
fix top level attr spans #36539
Conversation
r? @pnkfelix (rust_highfive has picked a reviewer for you, use r? to override) |
LGTM @bors r+ rollup |
📌 Commit 82639d4 has been approved by |
fix top level attr spans issue rust-lang#36530 ?r @jonathandturner
⌛ Testing commit 82639d4 with merge 9a760df... |
💔 Test failed - auto-win-gnu-32-opt-rustbuild |
@bors retry Seems like something didn't get cleaned up from a previous build |
fix top level attr spans issue rust-lang#36530 ?r @jonathandturner
fix top level attr spans issue rust-lang#36530 ?r @jonathandturner
@jonathandturner should I do something to merge the PR? |
@mikhail-m1 - I think you're probably okay. I tried doing a few rollups but they failed because other PRs in the rollup failed. |
fix top level attr spans issue rust-lang#36530 ?r @jonathandturner
The linux buildbot failed today because of this PR. |
The problem seems to be that the test during |
Never mind, the actual problem is that the missing lines are not printed when stability is overridden with a bootstrap key, I think. |
emit feature help in cheat mode (fix nightlies) This should fix the `distcheck` failure in the latest nightly. cc #36539 It's probably not ideal to check the environment that often and the code ist duplicated from `librustc/session/config.rs` but this was the easiest fix I could think of. A cleaner solution would probably be to move the `unstable_features` from `Options` to `ParseSess` and change the `diag` parameter of `emit_feature_err` to take `ParseSess` instead of a `Handler`.
issue #36530
?r @jonathandturner