-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Rollup of 5 pull requests #124170
Rollup of 5 pull requests #124170
Conversation
This needs to start downloading the descriptions after aliases have been added to the result set.
It's looks overkill to use rayon to collect cpu usage
(this currently produces malformed mir: we call `eq` with first argument not being a reference)
…, r=compiler-errors Correctly change type when adding adjustments on top of `NeverToAny` I'm concerned that the check only caught the problem with `fallback = !`, because at least MIR contained `<() as PartialEq>::eq(move _5, move _7)` where `_5: ()`. I rediscovered the issue when looking at rust-lang#123482's crater run. r? compiler-errors Fixes rust-lang#120600
run-make: refactor out command wrappers for `clang` and `llvm-readobj` This PR is rebased on top of rust-lang#123699. This PR is a follow up to rust-lang#123612 to refactor out command wrappers into the support library for `llvm-readobj` and `clang`. r? ghost
…p, r=oli-obk Don't repeatedly duplicate TAIT lifetimes for each subsequently nested TAIT Make it so that nested TAITs inherit the lifetimes from their parent item, not their parent TAIT. This is because we don't need to re-duplicate lifetimes for nested TAITs over and over, since the only lifetimes they can capture are from the parent item anyways. This mirrors how RPITs work. This is **not** a functional change that should be observable, since the whole point of duplicating lifetimes and marking the shadowed ones (and uncaptured ones) as bivariant is designed to *not* be observable. r? oli-obk
…GuillaumeGomez rustdoc-search: fix description on aliases in results This needs to start downloading the descriptions after aliases have been added to the result set.
…arsan68 bootstrap: don't use rayon for sysinfo It's looks overkill to use rayon to collect cpu usage
@bors r+ rollup=never p=5 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: ce3263e60e In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (f9b1614): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. 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: 672.283s -> 671.274s (-0.15%) |
Successful merges:
NeverToAny
#123571 (Correctly change type when adding adjustments on top ofNeverToAny
)clang
andllvm-readobj
#123729 (run-make: refactor out command wrappers forclang
andllvm-readobj
)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup