-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
rustc_passes: Enforce rustc::potential_query_instability
lint
#118870
Conversation
Stop allowing `rustc::potential_query_instability` in all of `rustc_passes` and instead allow it on a case-by-case basis if it is safe. In this case, all instances of the lint are safe to allow.
r? @b-naber (rustbot has picked a reviewer for you, use r? to override) |
r? compiler-errors @bors r+ |
…ty, r=compiler-errors rustc_passes: Enforce `rustc::potential_query_instability` lint Stop allowing `rustc::potential_query_instability` in all of `rustc_passes` and instead allow it on a case-by-case basis if it is safe. In this case, all instances of the lint are safe to allow. Part of rust-lang#84447 which is E-help-wanted.
@@ -1048,6 +1048,9 @@ pub fn check_unused_or_stable_features(tcx: TyCtxt<'_>) { | |||
tcx.sess.emit_err(errors::UnknownFeature { span, feature: *feature }); | |||
} | |||
|
|||
// We only use the hash map contents to emit errors, and the order of | |||
// emitted errors do not affect query stability. | |||
#[allow(rustc::potential_query_instability)] |
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.
Having different outputs for different platforms is a bug, even for diagnostics.
☀️ Test successful - checks-actions |
Finished benchmarking commit (c3def26): comparison URL. Overall result: ❌ regressions - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Warning ⚠: The following benchmark(s) failed to build:
cc @rust-lang/wg-compiler-performance Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis 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.
CyclesResultsThis 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: 671.712s -> 672.982s (0.19%) |
This is the periodical "slow s3 uploads on the collector", nothing to worry about: the timeouts are not due to this PR. There are no functional changes here in the first place. @rustbot label: +perf-regression-triaged |
Stop allowing
rustc::potential_query_instability
in all ofrustc_passes
and instead allow it on a case-by-case basis if it is safe. In this case, all instances of the lint are safe to allow.Part of #84447 which is E-help-wanted.