-
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
Nix rustc_hir
reexports in rustc::hir
#67886
Conversation
25c0999
to
91fa014
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
bf953f3
to
0156368
Compare
Seems to be passing now..., finally :) |
@bors r+ |
📌 Commit 0156368 has been approved by |
r? @nagisa |
Raising the prio of this a bit because it's blocking other work and because it's bit-rotty. @bors p=1 |
⌛ Testing commit 0156368 with merge d6e24cb7218cfdc7f8e1563df7f34b128be14049... |
💔 Test failed - checks-azure |
@bors retry seems spurious. |
☀️ Test successful - checks-azure |
📣 Toolstate changed by #67886! Tested on commit ebbb2bf. 💔 clippy-driver on windows: test-pass → build-fail (cc @mcarton @oli-obk @Manishearth @flip1995 @yaahc @phansch @llogiq, @rust-lang/infra). |
Tested on commit rust-lang/rust@ebbb2bf. Direct link to PR: <rust-lang/rust#67886> 💔 clippy-driver on windows: test-pass → build-fail (cc @mcarton @oli-obk @Manishearth @flip1995 @yaahc @phansch @llogiq, @rust-lang/infra). 💔 clippy-driver on linux: test-pass → build-fail (cc @mcarton @oli-obk @Manishearth @flip1995 @yaahc @phansch @llogiq, @rust-lang/infra).
Rustup to rust-lang/rust#67886 changelog: none
Rustup to rust-lang/rust#67886 changelog: none
It makes for confusing code. This was introduced in a large commit in rust-lang#67886 that rearranged a lot of `use` statements. I suspect it was an accident.
…t, r=fee1-dead Don't `use rustc_hir as ast`(!) It makes for confusing code. This was introduced in a large commit in rust-lang#67886 that rearranged a lot of `use` statements. I suspect it was an accident.
r? @Zoxc cc @Mark-Simulacrum