-
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 #113223
Rollup of 5 pull requests #113223
Conversation
…, r=cjgillot Make simd_shuffle_indices use valtrees This removes the second-to-last user of the `destructure_mir_constant` query. So in a follow-up we can remove the query and just move the query provider function directly into pretty printing (which is the last user). cc ``@rust-lang/clippy`` there's a small functional change, but I think it is correct?
…next, r=compiler-errors Better messages for next on a iterator inside for loops Fixes rust-lang#102972
…=thomcc Backtrace 0.3.68 Uptakes these releases: - https://github.com/rust-lang/backtrace-rs/releases/tag/0.3.68 - https://github.com/rust-lang/flate2-rs/releases/tag/1.0.26 r? `@thomcc`
…ures, r=oli-obk Error when RPITITs' hidden types capture more lifetimes than their trait definitions This implements a stricter set of captures rules for RPITITs. They now may only capture: 1. Lifetimes from the impl header (both the self type and any trait substs -- we may want to restrict just to the self type's lifetimes, but the PR makes that easy to do, too) 2. Lifetimes mentioned by the `impl Trait` in the trait method's definition. Namely, they may not mention lifetimes from the method (early or late) that are not mentioned in the `impl Trait`. cc rust-lang#105258 which I think was trying to do this too, though I'm not super familiar with what exactly differs from that or why that one was broken. cc rust-lang#112194 (doesn't fix this issue per se, because it's still an open question, but I think this is objectively better than the status quo, and gets us closer to resolving that issue.) Technically is a fix for the ICE in rust-lang#108580, but it turns that issue into an error now. We can decide separately whether or not nested RPITITs should capture lifetimes from their parents. r? `@oli-obk`
Fix associated items effective visibility calculation for type privacy lints Fixes rust-lang#113126 (comment).
@bors r+ rollup=never p=5 |
The job Click to see the possible cause of the failure (guessed by this bot)
|
⌛ Testing commit 181861c with merge 43fd7c9a30612f9036c9a6a513dfd12c47a89963... |
@bors retry |
⌛ Testing commit 181861c with merge ad60dcc77d36d5342bdf2871e77fd06d566d4113... |
💔 Test failed - checks-actions |
@bors retry |
⌛ Testing commit 181861c with merge 6a1af3eed86a8cf67ceafd847d8be14c97c59646... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors retry |
⌛ Testing commit 181861c with merge 505c197a9e1fa4d836678e0e7fad07e948a3ee8e... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
Successful merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup