Conversation
The only regression is one ambiguity in the new trait solver, having to do with two param-env candidates that may apply. I think this is fine, since the error message already kinda sucks.
Implement proposed API for `proc_macro_span` As proposed in [rust-lang#54725 (comment)](rust-lang#54725 (comment)). I have omitted the byte-level API as it's already available as [`Span::byte_range`](https://doc.rust-lang.org/nightly/proc_macro/struct.Span.html#method.byte_range). `@rustbot` label +A-proc-macros r? `@m-ou-se`
Simplify computation of killed borrows Follow-up to rust-lang#111759 Processing the first block manually once makes the pre-order walk simpler.
…its, r=lcnr More `ImplSource` nits Even more clean-ups, I'll put this up in parallel with the `select_in_new_trait_solver` PR. r? ``@lcnr``
…on-exhaustion, r=fee1-dead add note for non-exhaustive matches with guards Associated issue: rust-lang#92197 When a match statement includes guards on every match arm (and is therefore necessarily non-exhaustive), add a note to the error E0004 diagnostic noting this.
…-in-head, r=notriddle,fmease Fix invalid HTML DIV tag used in HEAD Fixes rust-lang#113067. The issue also nicely explains the whole problem. r? ``@notriddle``
…piler-errors add myself to review for t-types stuff I think this is how the triagebot stuff works 😅 should mean that `r? types` can now assign me
|
@bors r+ rollup=never p=5 |
|
☀️ Test successful - checks-actions |
|
📌 Perf builds for each rolled up PR:
previous master: 8882507bc7 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
Finished benchmarking commit (eb76764): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. 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: 662.642s -> 663.439s (0.12%) |
Successful merges:
proc_macro_span#111571 (Implement proposed API forproc_macro_span)ImplSourcenits #112867 (MoreImplSourcenits)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup