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
Uplift AliasTy
and AliasTerm
#125088
Uplift AliasTy
and AliasTerm
#125088
Conversation
This comment has been minimized.
This comment has been minimized.
9655d3a
to
5da646b
Compare
This comment has been minimized.
This comment has been minimized.
d44c4fd
to
1b9baca
Compare
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.
r=me after nit
1b9baca
to
9f8cdb2
Compare
@bors r=lcnr |
…mpiler-errors Rollup of 7 pull requests Successful merges: - rust-lang#119838 (style-guide: When breaking binops handle multi-line first operand better) - rust-lang#124844 (Use a proper probe for shadowing impl) - rust-lang#125047 (Migrate `run-make/issue-14500` to new `rmake.rs` format) - rust-lang#125080 (only find segs chain for missing methods when no available candidates) - rust-lang#125088 (Uplift `AliasTy` and `AliasTerm`) - rust-lang#125100 (Don't do post-method-probe error reporting steps if we're in a suggestion) - rust-lang#125118 (Use new utility functions/methods in run-make tests) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#125088 - compiler-errors:uplift-alias-ty, r=lcnr Uplift `AliasTy` and `AliasTerm` Follow-up from rust-lang#125076. r? lcnr
@rust-timer build 3dd3328 |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (3dd3328): comparison URL. Overall result: ❌✅ regressions and improvements - 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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never 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)This benchmark run did not return any relevant results for this metric. CyclesResults (primary 0.6%)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: 676.581s -> 679.283s (0.40%) |
@compiler-errors @lcnr have we decided that the perf regression is too small to worry about here? |
I think so, yeah |
@rustbot label: +perf-regression-triaged |
Follow-up from #125076.
r? lcnr