-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rollup of 8 pull requests #113474
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 8 pull requests #113474
Conversation
…e in bad positions
…, r=albertlarsan68 Add needs-triage to all new issues Closes rust-lang#113261 The label: https://github.com/rust-lang/rust/labels/needs-triage
…, r=fee1-dead Don't ICE in `resolve_bound_vars` when associated return-type bounds are in bad positions I couldn't find a better way to avoid hitting this ICE, so let's just delay it. The problem is that we really shouldn't even be *trying* to visit associated type bounds in `resolve_bound_vars` when they show up in impl headers, but we don't have enough context to do this. Fixes rust-lang#113423
…itit-gat, r=spastorino Remove `variances_of` on RPITIT GATs, remove its one use-case It doesn't make sense to implement variances on a GAT anyways, since we don't relate GATs with variance: https://github.com/rust-lang/rust/blob/85bf07972a1041b9e25393b803d0e006bec3eaaf/compiler/rustc_middle/src/ty/relate.rs#L569-L579 r? ``@spastorino``
miri: check that assignments do not self-overlap r? `````@oli-obk`````
…er-errors Remove unused from_method from rustc_on_unimplemented Fixes rust-lang#113439 `on_unimplemented_note` was calling `item_name` for RPITITs and that produced ICEs. I've added a regression test for that but also have removed `from_method` symbol entirely because it wasn't even used and by doing that the `item_name` call was also removed. r? ``@compiler-errors``
…er-errors Avoid calling report_forbidden_specialization for RPITITs Fixes rust-lang#113438 r? ``@compiler-errors``
Update cargo 1 commits in 5b377cece0e0dd0af686cf53ce4637d5d85c2a10..45782b6b8afd1da042d45c2daeec9c0744f72cc7 2023-06-30 00:01:00 +0000 to 2023-07-05 16:54:51 +0000 - docs(ref): Provide guidance on version requirements (rust-lang/cargo#12323) r? ``@ghost``
Fix comment of `fn_can_unwind` Reopen of rust-lang#113213
@bors r+ rollup=never p=8 |
⌛ Testing commit 7a22c7e with merge 99ebfe3778dd0d2bcae8c7dc023025a305a177bd... |
💥 Test timed out |
☀️ Test successful - checks-actions |
1 similar comment
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: d4096e0412 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (ce519c5): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression 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)ResultsThis 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.
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: 656.508s -> 655.094s (-0.22%) |
Successful merges:
resolve_bound_vars
when associated return-type bounds are in bad positions #113426 (Don't ICE inresolve_bound_vars
when associated return-type bounds are in bad positions)variances_of
on RPITIT GATs, remove its one use-case #113427 (Removevariances_of
on RPITIT GATs, remove its one use-case)fn_can_unwind
#113467 (Fix comment offn_can_unwind
)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup