only next-solver: move implied bounds computation out of borrowck - #161047
only next-solver: move implied bounds computation out of borrowck#161047lcnr wants to merge 5 commits into
Conversation
|
|
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
only next-solver: move implied bounds computation out of borrowck
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (64561ff): comparison URL. Overall result: ❌✅ regressions and improvements - please read:Benchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf. Next, please: If you can, justify the regressions found in this try perf run in writing along with @bors rollup=never rustc-perf Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 0.4%, secondary -0.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -0.5%, secondary 2.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 455.615s -> 458.36s (0.60%) |
This comment has been minimized.
This comment has been minimized.
to enable the new solver for testing without needing to FCP the changes to the old one.
e77a2d7 to
457c9db
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
@bors r=adwinwhite |
version of #160491 which does not enable this change for the old solver, meaning that we can merge it without a types team FCP :>
r? adwinwhite