-
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 5 pull requests #95382
Rollup of 5 pull requests #95382
Conversation
* Add lazily computed `switch_sources` data structure * Don't assume a target has only one associated value
Copying the pattern from `Vec::try_reserve_exact` and `String::try_reserve`, it looks like this doc comment is intending to refer to the currently-being-documented function.
…stion, r=cjgillot diagnostics: suggest missing comma in bad FRU syntax Fixes rust-lang#51103
…tatic-morse Implement `apply_switch_int_edge_effects` for backward analyses See rust-lang#94576 for some discussion. r? `@ecstatic-morse`
…on-e0667, r=Dylan-DPC Add long error explanation for E0667 Part of rust-lang#61137.
Remove test files with duplicated checksums cc rust-lang#73494 r? `@petrochenkov`
…e-exact-doc-typo, r=Dylan-DPC Fix typo in `String::try_reserve_exact` docs Copying the pattern from `Vec::try_reserve_exact` and `String::try_reserve`, it looks like this doc comment is intending to refer to the currently-being-documented function.
@bors r+ rollup=never p=5 |
📌 Commit eca2531 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (6252304): comparison url. Summary: This benchmark run shows 4 relevant improvements 🎉 but 7 relevant regressions 😿 to instruction counts.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression |
Visiting for weekly performance triage. Changes to the primary benchmarks seem like a wash and probably ignorable (0.33% worse for unicode-normalization-0.1.19, 0.33% better for ripgrep-13.0.0). Changes to the secondary benchmarks are slightly more concerning: namely, 3% worse for await-call-tree (on six scenarios). If I had to guess, I'd assume that this impact was caused by PR #95120; the other PRs in this rollup seem very innocuous, while PR #95120 is (slightly(?)) more invasive. I'm going to leave this as untriaged for now. |
Successful merges:
apply_switch_int_edge_effects
for backward analyses #95120 (Implementapply_switch_int_edge_effects
for backward analyses)String::try_reserve_exact
docs #95368 (Fix typo inString::try_reserve_exact
docs)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup