Rollup of 8 pull requests #90165
Closed
Rollup of 8 pull requests #90165
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It's a visitor property rather than something that needs to be determined at runtime
The const qualification was so far performed before the promotion and the implementation assumed that it will never encounter a promoted. With `const_precise_live_drops` feature, checking for live drops is delayed until after drop elaboration, which in turn runs after promotion. so the assumption is no longer true. When evaluating `NeedsNonConstDrop` it is now possible to encounter promoteds. Use type base qualification for the promoted. It is a sound approximation in general, and in the specific case of promoteds and `NeedsNonConstDrop` it is precise.
rustbot doesn't allow unauthenticated users to set `I-nominated`; apply the same permissions to the new `I-*nominated` labels.
Previously, it wasn't clear whether "This could include" was referring to logic errors, or undefined behaviour. Tweak wording to clarify this sentence does not relate to UB.
…rk-Simulacrum Clarify undefined behaviour in binary heap, btree and hashset docs Previously, it wasn't clear whether "This could include" was referring to logic errors, or undefined behaviour. Tweak wording to clarify this sentence does not relate to UB.
Update E0637 description to mention `&` w/o an explicit lifetime name Deal with rust-lang#89824 (comment). Another solution would be splitting the error code into two as (I think) it's a bit unclear to users why they have the same error code.
rustc_ast: Turn `MutVisitor::token_visiting_enabled` into a constant It's a visitor property rather than something that needs to be determined at runtime
…i-obk Fix const qualification when executed after promotion The const qualification was so far performed before the promotion and the implementation assumed that it will never encounter a promoted. With `const_precise_live_drops` feature, checking for live drops is delayed until after drop elaboration, which in turn runs after promotion. so the assumption is no longer true. When evaluating `NeedsNonConstDrop` it is now possible to encounter promoteds. Use type base qualification for the promoted. It is a sound approximation in general, and in the specific case of promoteds and `NeedsNonConstDrop` it is precise. Fixes rust-lang#89938.
…crum Add a regression test for issue-83479 Add a regression test for rust-lang#83479 (comment), but not close the issue, see rust-lang#83479 (comment).
Add some tests for const_generics_defaults I think this covers some of the stuff required for stabilisation report, some of these tests are probably covering stuff we already have but it can't hurt to have more :) r? `````@lcnr`````
Add test for issue rust-lang#78561 Adds test for and closes rust-lang#78561 which previously crashed compiler.
…=Mark-Simulacrum triagebot: Treat `I-*nominated` like `I-nominated` rustbot doesn't allow unauthenticated users to set `I-nominated`; apply the same permissions to the new `I-*nominated` labels.
|
@bors r+ p=8 rollup=never |
|
📌 Commit d3b9a1a has been approved by |
bors
added
the
S-waiting-on-bors
|
this rollup intersects with #90161 |
|
⌛ Testing commit d3b9a1a with merge 67a1eef3f6a3cb826fda7f5f813deef165e089d7... |
|
Oh sorry, I forgot to r+ my rollup 😅 @bors retry yielding |
bors
added
S-waiting-on-author
|
Yeah, let's close not to have duplicate work. |
|
I would have kept this open for maybe 2 hours, in case 90161 fails bors would start with that one right after. |
|
If both are merged, it would be confusing to tell which PRs are merged with which rollup. |
|
Sure but we have more than 3 hours to kill the second rollup in time ^^ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Successful merges:
&w/o an explicit lifetime name #89922 (Update E0637 description to mention&w/o an explicit lifetime name)MutVisitor::token_visiting_enabledinto a constant #89991 (rustc_ast: TurnMutVisitor::token_visiting_enabledinto a constant)region is not an ReVar: ReEarlyBound(0, 'a)with type_alias_impl_trait and particular type parameter bounds #78561)I-*nominatedlikeI-nominated#90129 (triagebot: TreatI-*nominatedlikeI-nominated)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup