-
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
Rollup of 6 pull requests #100540
Rollup of 6 pull requests #100540
Conversation
Recover from mutable variable declaration where `mut` is placed before `let`
In rust-lang#100513 it was shown that the drop behavior of let_chains is not correct currently. Since drop behavior is something pretty subtle, this adds explicit tests for the drop behavior of `if`, `if let` and `match` to make sure that it does not regress in the future. The `println!`s were left in to make debugging easier in case something goes wrong, but they are not required for the test.
Fix HorizonOS regression in FileTimes The changes in rust-lang#98246 caused a regression for multiple Newlib-based systems. This is just a fix including HorizonOS to the list of targets which require a workaround. ``@AzureMarker`` ``@ian-h-chamberlain`` r? ``@nagisa``
Recover from mutable variable declaration where `mut` is placed before `let` Closes rust-lang#100197
Add Duration rounding change to release note one of possible fix of rust-lang#100480 fixes rust-lang#100480
… r=Dylan-DPC [rustdoc] remove Clean trait Follow-up of rust-lang#99638. This is (finally!) the last part. r? `@Dylan-DPC`
…ild-structs, r=Mark-Simulacrum Impl `Debug` for some structs of rustbuild A small patch to impl `Debug` for some structs of rustbuild to make debugging easier. (I was trying to impl `Debug` for the `Config` struct, but found to have a bit more things to do. So gave up for now.)
Add tests for the drop behavior of some control flow constructs In rust-lang#100513 it was shown that the drop behaviour of let_chains is not correct currently. Since drop behaviour is something pretty subtle, this adds explicit tests for the drop behavior of `if`, `if let` and `match` to make sure that it does not regress in the future. The `println!`s were left in to make debugging easier in case something goes wrong, but they are not required for the test.
@bors r+ rollup=never p=6 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (b8c0a01): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
Successful merges:
mut
is placed beforelet
#100253 (Recover from mutable variable declaration wheremut
is placed beforelet
)Debug
for some structs of rustbuild #100524 (ImplDebug
for some structs of rustbuild)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup