-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Handle rustc_middle
cases of rustc::potential_query_instability
lint
#131160
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
base: master
Are you sure you want to change the base?
Handle rustc_middle
cases of rustc::potential_query_instability
lint
#131160
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @compiler-errors (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. Some changes occurred in src/tools/clippy cc @rust-lang/clippy |
This comment has been minimized.
This comment has been minimized.
da9a8fd
to
4c46978
Compare
This comment has been minimized.
This comment has been minimized.
4c46978
to
afeabb2
Compare
e8cc67a
to
0000613
Compare
☔ The latest upstream changes (presumably #131263) made this pull request unmergeable. Please resolve the merge conflicts. |
0000613
to
01e27a3
Compare
☔ The latest upstream changes (presumably #132282) made this pull request unmergeable. Please resolve the merge conflicts. |
I'm gonna re-roll this so this PR gets more attention, sorry for my inactivity. r? compiler But also reassigning to author sicne I think this PR still needs updating. @rustbot author |
@ismailarilik Can you rebase the PR today? I'm in holiday tomorrow so I"d like to have a review before that :) |
r? compiler cause I'm going to the holidays in the next few days. And I suggest to run a rustc perf when it's ready since this PR change the cache struct |
@ismailarilik any updates on this? thanks |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
ccae5e3
to
095de4a
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
095de4a
to
6f1b172
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
How can I update "*.fixed" files? |
I believe the failing tests are clippy tests, not rustc/compiletest tests. You may need to rebless clippy tests via something like $ ./x test clippy --bless |
6d87d32
to
6bf8881
Compare
r? query-system |
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
…instability-lint-for-rustc-middle, r=<try> Handle `rustc_middle` cases of `rustc::potential_query_instability` lint This PR removes `#![allow(rustc::potential_query_instability)]` line from [`compiler/rustc_middle/src/lib.rs`](https://github.com/rust-lang/rust/blob/master/compiler/rustc_middle/src/lib.rs#L29) and converts `FxHash{Map,Set}` types into `FxIndex{Map,Set}` to suppress lint errors. A somewhat tracking issue: rust-lang#84447 r? `@compiler-errors`
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (9d711dc): comparison URL. Overall result: ❌✅ regressions and improvements - no action neededBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary -0.1%, secondary -0.8%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResults (primary -0.2%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 768.358s -> 769.173s (0.11%) |
@@ -3520,6 +3520,8 @@ pub fn trimmed_def_paths(tcx: TyCtxt<'_>, (): ()) -> DefIdMap<Symbol> { | |||
|
|||
// Put the symbol from all the unique namespace+symbol pairs into `map`. | |||
let mut map: DefIdMap<Symbol> = Default::default(); | |||
// Precatious is taken below in the loop so we can allow this lint here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// Precatious is taken below in the loop so we can allow this lint here. | |
// Precautions are taken below in the loop so we can allow this lint here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tho this is only used in diagnostics, right? we could just use an IndexMap for unique_symbols_rev
, too?
This PR removes
#![allow(rustc::potential_query_instability)]
line fromcompiler/rustc_middle/src/lib.rs
and convertsFxHash{Map,Set}
types intoFxIndex{Map,Set}
to suppress lint errors.A somewhat tracking issue: #84447
r? @compiler-errors