-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rollup of 6 pull requests #111040
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 #111040
Conversation
Add test checking that it is possible to capture fields of a multi-variant enum, when remaining variants are visibly uninhabited (under the `exhaustive_patterns` feature gate).
HIR pretty printing already handles it correctly.
…r=b-naber Tweak await span to not contain dot Fixes a discrepancy between method calls and await expressions where the latter are desugared to have a span that *contains* the dot (i.e. `.await`) but method call identifiers don't contain the dot. This leads to weird suggestions suggestions in borrowck -- see linked issue. Fixes rust-lang#110761 This mostly touches a bunch of tests to tighten their `await` span.
…er-errors Remove wrong assertion in match checking. This assertions is completely misguided, introduced by rust-lang#108504. The responsible PR is on beta, nominating for backport. Instead of checking that this is not a `&&`, it would make sense to check that neither arms of that `&&` is a `let`. This seems like a lot of code for unclear benefit. r? `@saethlin`
…ompiler-errors Test precise capture with a multi-variant enum and exhaustive patterns Add test checking that it is possible to capture fields of a multi-variant enum, when remaining variants are visibly uninhabited (under the `exhaustive_patterns` feature gate).
… r=compiler-errors Migrate `builtin_macros::asm` diagnostics to translatable diagnostics cc rust-lang#100717 Planning on working through the remaining diagnostics in this crate
…ompiler-errors Ping Nadrieril when changing exhaustiveness checking Hi! I don't know what the procedure is but I'd quite like to be pinged when people try to change the exhaustiveness code. It's a tricky piece of code and I'm the de facto expert on it; I'd like to be available to provide feedback to contributors who wish to change it. I occasionally look through the git history and open PRs but a triagebot ping would be much more convenient. The message says "might have" because `check_match.rs` contains a little bit of exhaustiveness logic and a lot of other match-related checks, so this ping will have false positives.
…mpiler-errors Close parentheses for `offset_of` in AST pretty printing HIR pretty printing already handles it correctly. This will conflict with rust-lang#110694 but it seems like that PR is gonna take bit more time.
@bors r+ rollup=never p=6 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: 9ecda8de85 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (2034b6d): comparison URL. Overall result: ❌ regressions - 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.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 656.939s -> 655.48s (-0.22%) |
Successful merges:
builtin_macros::asm
diagnostics to translatable diagnostics #111032 (Migratebuiltin_macros::asm
diagnostics to translatable diagnostics)offset_of
in AST pretty printing #111037 (Close parentheses foroffset_of
in AST pretty printing)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup