Rollup of 4 pull requests#156881
Conversation
The lint suggestion now removes the `+` joiner adjacent to a redundant `use<...>` clause, so applying the suggestion does not leave a dangling `+` that fails to parse. The existing `tests/ui/impl-trait/precise-capturing/redundant.stderr` baseline emits the same diagnostic with the expanded suggestion span and is blessed along with the new `run-rustfix` test. Tested: - ./x test tests/ui/impl-trait/precise-capturing/redundant.rs --force-rerun - ./x test tests/ui/impl-trait/precise-capturing/redundant-machine-applicable.rs --force-rerun - ./x test tidy
…se, r=Urgau,jhpratt Parse `mut` restrictions This PR is part of the progress implementing `mut` restrictions proposed in [RFC 3323](https://rust-lang.github.io/rfcs/3323-restrictions.html), and linked to a [GSoC proposal](https://rust-lang.zulipchat.com/#narrow/channel/421156-gsoc/topic/Project.3A.20Implementing.20impl.20and.20mut.20restrictions/with/592352432). This PR focuses solely on the parsing of `mut` restrictions. The keyword order is `pub(...) mut(...) unsafe field`. The new syntax is guared by `#[feature(mut_restriction)]` feature gate. Tracking Issue: rust-lang#105077 r? @Urgau cc @jhpratt
…apin Fix doc typo in Vec::into_array and convert Arc/Box/Rc::into_arry to -> Result Hello 🪼, the first commit fixes a documentation mistake added in the recent PR rust-lang#156234 The second commit addresses three function signature changes as defined by the tracking issue rust-lang#148082 It converts all `.into_array() -> Option<>` into `.into_array() -> Result<>` The third commit is a fixup for the second. The change is needed as calling `unwrap()` on `Err(E)` requires `E` to implement `Debug`. I thought `Vec<T, A> where T: Debug` is not an acceptable solution, so I tried to come up with my own. I am *NOT* confident in my `unsafe {}` code due to lack of expierence, please check extra carefully. Appreciating feedback & greetings from the RustWeek, Thanks!
Add regression test for const parameter default ICE Closes rust-lang#142913 This adds a UI regression test for a fixed ICE where a const generic parameter type mentioned an earlier lifetime and also had a default value. The reproducer is the minimized version posted in the issue. Tested: - ./x test tests/ui/const-generics/generic_const_parameter_types/region-parameter-out-of-range-ice-142913.rs --force-rerun - ./x test tidy --bless
…6, r=cjgillot Make impl_trait_redundant_captures suggestion remove adjacent + Closes rust-lang#143216 The `impl_trait_redundant_captures` lint's machine-applicable suggestion only spanned the `use<...>` syntax itself, leaving the adjacent `+` joiner behind. Applying the suggestion produced uncompilable code, e.g. `impl Sized + use<>` becoming `impl Sized + ` (stray trailing `+`). This extends the removal span to also cover one adjacent `+`, preserving valid syntax in the three bound-list positions covered by the regression test: - `impl Sized + use<>` becomes `impl Sized` - `impl use<> + Sized` becomes `impl Sized` - `impl Sized + use<> + Send` becomes `impl Sized + Send` A `//@ run-rustfix` UI test exercises all three positions, so the rustfix-applied output is actually compiled — covering the gap the existing `redundant.rs` test left (which only checks lint firing, not suggestion correctness). Tested: - ./x test tests/ui/impl-trait/precise-capturing/redundant-machine-applicable.rs --bless - ./x test tidy
|
@bors r+ rollup=never p=5 |
This comment has been minimized.
This comment has been minimized.
|
📌 Perf builds for each rolled up PR:
previous master: 1d59f669f9 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 1d59f66 (parent) -> 609b8c5 (this PR) Test differencesShow 1074 test diffsStage 1
Stage 2
Additionally, 1064 doctest diffs were found. These are ignored, as they are noisy. Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 609b8c5cefb3932bbaf4497cb7f9195ca8a1eab6 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (609b8c5): comparison URL. Overall result: ❌ regressions - please read:Our benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 3.3%, secondary -2.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -2.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 510.511s -> 508.631s (-0.37%) |
Successful merges:
mutrestrictions #156824 (Parsemutrestrictions)r? @ghost
Create a similar rollup