Skip to content

Conversation

@matthiaskrgr
Copy link
Member

@matthiaskrgr matthiaskrgr commented Nov 27, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

yoshuawuyts and others added 16 commits November 6, 2025 17:27
Also changes it from a static method to an instance method.
…raph

Currently, If `expected_def_id` and `another_trait_def_id` have their
crate imported as ExternCrateSource::Path the method
get_extern_crate_renamed_symbol() will return None for both, resulting
in a false positive. This fixes the issue by using a slitly different
approach, we use a predicate instead and do the comparison of the item
names only when both crates are imported as ExternCrateSource::Extern and
are direct dependencies of the LOCAL_CRATE, otherwise false is returned.
Relocate issues/issue-51022.rs to
entry-point/main-with-lifetime-param.rs

Relocate issue-50714.rs to entry-point/main-where-fn-bound.rs

Rename issue-118772.rs to main-with-invalid-signature.rs and delete
duplicate test

remove ui/entry-point/issue-118772.rs in issues.txt

Relocate fn-main/wrong-location.rs to entry-point/main-in-submodule.rs

Remove fn-main directory

Relocate issue-50688.rs to mismatched_types/array-len-is-closure.rs
…ffleLapkin

remove support for `typeof`

see rust-lang/compiler-team#940 closes rust-lang#148700

This also enables checks for invariants previously broken by `typeof` again.

r? types
…oshtriplett

Rename `DropGuard::into_inner` to `DropGuard::dismiss`

Tracking issue: rust-lang#144426

One of the open questions blocking the stabilization of `DropGuard` is what to name the associated method that prevents the destructor from running, and returns the captured value. This method is currently called `into_inner`, but most people (including myself) feel like this would benefit from a method that calls more attention to itself.

This PR proposes naming this method `dismiss`, after the Linux kernel's [`ScopeGuard::dismiss`](https://rust.docs.kernel.org/kernel/types/struct.ScopeGuard.html#method.dismiss). Which crucially does not evoke images of violence or weaponry the way alternatives such as "disarm" or "defuse" do. And personally I enjoy the visual metaphor of "dismissing a guard" (e.g. a person keeping watch over something) - a job well done, they're free to go.

This PR also changes the signature from an static method to an instance method. This also matches the Linux kernel's API, and seems alright since `dismiss` is not nearly as ubiquitous as `into_inner`. This makes it more convenient to use, with a much lower risk of conflicting. Though in the rare case there might be ambiguity, the explicit notation is available as a fallback.

```rust
let x = DropGuard::into_inner(guard);  // ← current
let x = guard.dismiss();               // ← proposed
…ent_versions_of_crate, r=lcnr

Fix false positive of "multiple different versions of crate X in the dependency graph"

cc rust-lang#148892
fix ICE: rustdoc: const parameter types cannot be generic rust-lang#149288

fix rust-lang#149288

Applied the patch.
Deeply normalize param env in `compare_impl_item` if using the next solver

Fixes rust-lang/trait-system-refactor-initiative#166.

Duplicated the `normalize_param_env_or_error` function to force deep normalization for `compare_impl_item`.

r? `@lcnr`
Tidying up UI tests [4/N]

> [!NOTE]
> Intermediate commits are intended to help review, but will be squashed prior to merge.

part of rust-lang#133895

Relocate 4 tests in fn-main and issues and remove fn-main directory

r? Kivooeo
@rustbot rustbot added A-tidy Area: The tidy tool S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-clippy Relevant to the Clippy team. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output. T-rustfmt Relevant to the rustfmt team, which will review and decide on the PR/issue. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver) rollup A PR which is a rollup labels Nov 27, 2025
@matthiaskrgr
Copy link
Member Author

@bors r+ rollup=never p=5

@bors
Copy link
Collaborator

bors commented Nov 27, 2025

📌 Commit 01512aa has been approved by matthiaskrgr

It is now in the queue for this repository.

@bors bors removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Nov 27, 2025
@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Nov 27, 2025
@bors
Copy link
Collaborator

bors commented Nov 27, 2025

⌛ Testing commit 01512aa with merge f392ed5...

@bors
Copy link
Collaborator

bors commented Nov 27, 2025

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing f392ed5 to main...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Nov 27, 2025
@bors bors merged commit f392ed5 into rust-lang:main Nov 27, 2025
12 checks passed
@rustbot rustbot added this to the 1.93.0 milestone Nov 27, 2025
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#148256 remove support for typeof 7dd9c3b44a275d4bec2ff33f99635861438e7fd0 (link)
#148589 Rename DropGuard::into_inner to DropGuard::dismiss d50ab145eaf967b53262c9b021d1089de26a5681 (link)
#149001 Fix false positive of "multiple different versions of crate… 9d7e179ac0ed45ad47bbecd89b50d4efab728e67 (link)
#149334 fix ICE: rustdoc: const parameter types cannot be generic #… a86be95ca32fff10be4bfe8d3f36945df9242f40 (link)
#149345 Deeply normalize param env in compare_impl_item if using … 88a1941d3338808a459abada5c30daa2cacf6a1f (link)
#149367 Tidying up UI tests [4/N] 14dc65d61d1d889b635392604b35c8a28966585c (link)

previous master: cf8a95590a

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

@github-actions
Copy link
Contributor

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 cf8a955 (parent) -> f392ed5 (this PR)

Test differences

Show 108 test diffs

Stage 1

  • [rustdoc] tests/rustdoc/const-generics/const-param-type-references-generics.rs: [missing] -> pass (J1)
  • [ui] tests/rustdoc-ui/issues/ice-typeof-102986.rs: pass -> [missing] (J1)
  • [ui] tests/ui/closures/impl-closure-147146.rs: pass -> [missing] (J1)
  • [ui] tests/ui/entry-point/issue-118772.rs: pass -> [missing] (J1)
  • [ui] tests/ui/entry-point/main-in-submodule.rs: [missing] -> pass (J1)
  • [ui] tests/ui/entry-point/main-where-fn-bound.rs: [missing] -> pass (J1)
  • [ui] tests/ui/entry-point/main-with-invalid-signature.rs: [missing] -> pass (J1)
  • [ui] tests/ui/entry-point/main-with-lifetime-param.rs: [missing] -> pass (J1)
  • [ui] tests/ui/fn-main/wrong-location.rs: pass -> [missing] (J1)
  • [ui] tests/ui/fn-main/wrong-type.rs: pass -> [missing] (J1)
  • [ui] tests/ui/higher-ranked/trait-bounds/issue-100689.rs: pass -> [missing] (J1)
  • [ui] tests/ui/higher-ranked/trait-bounds/issue-100689.rs#next: [missing] -> pass (J1)
  • [ui] tests/ui/higher-ranked/trait-bounds/issue-100689.rs#old: [missing] -> pass (J1)
  • [ui] tests/ui/higher-ranked/trait-bounds/issue-102899.rs: pass -> [missing] (J1)
  • [ui] tests/ui/higher-ranked/trait-bounds/issue-102899.rs#next: [missing] -> pass (J1)
  • [ui] tests/ui/higher-ranked/trait-bounds/issue-102899.rs#old: [missing] -> pass (J1)
  • [ui] tests/ui/issues/issue-50688.rs: pass -> [missing] (J1)
  • [ui] tests/ui/issues/issue-50714.rs: pass -> [missing] (J1)
  • [ui] tests/ui/issues/issue-51022.rs: pass -> [missing] (J1)
  • [ui] tests/ui/mismatched_types/array-len-is-closure.rs: [missing] -> pass (J1)
  • [ui] tests/ui/traits/next-solver/normalize/deeply-normalize-env-in-compare-impl-item.rs: [missing] -> pass (J1)
  • [ui] tests/ui/traits/wrong-multiple-different-versions-of-a-crate.rs: [missing] -> pass (J1)
  • [ui] tests/ui/typeof/issue-100183.rs: pass -> [missing] (J1)
  • [ui] tests/ui/typeof/issue-29184.rs: pass -> [missing] (J1)
  • [ui] tests/ui/typeof/issue-42060.rs: pass -> [missing] (J1)
  • [ui] tests/ui/typeof/type_mismatch.rs: pass -> [missing] (J1)

Stage 2

  • [ui] tests/ui/closures/impl-closure-147146.rs: pass -> [missing] (J0)
  • [ui] tests/ui/entry-point/issue-118772.rs: pass -> [missing] (J0)
  • [ui] tests/ui/entry-point/main-in-submodule.rs: [missing] -> pass (J0)
  • [ui] tests/ui/entry-point/main-where-fn-bound.rs: [missing] -> pass (J0)
  • [ui] tests/ui/entry-point/main-with-invalid-signature.rs: [missing] -> pass (J0)
  • [ui] tests/ui/entry-point/main-with-lifetime-param.rs: [missing] -> pass (J0)
  • [ui] tests/ui/fn-main/wrong-location.rs: pass -> [missing] (J0)
  • [ui] tests/ui/fn-main/wrong-type.rs: pass -> [missing] (J0)
  • [ui] tests/ui/higher-ranked/trait-bounds/issue-100689.rs: pass -> [missing] (J0)
  • [ui] tests/ui/higher-ranked/trait-bounds/issue-100689.rs#next: [missing] -> pass (J0)
  • [ui] tests/ui/higher-ranked/trait-bounds/issue-100689.rs#old: [missing] -> pass (J0)
  • [ui] tests/ui/higher-ranked/trait-bounds/issue-102899.rs: pass -> [missing] (J0)
  • [ui] tests/ui/higher-ranked/trait-bounds/issue-102899.rs#next: [missing] -> pass (J0)
  • [ui] tests/ui/higher-ranked/trait-bounds/issue-102899.rs#old: [missing] -> pass (J0)
  • [ui] tests/ui/issues/issue-50688.rs: pass -> [missing] (J0)
  • [ui] tests/ui/issues/issue-50714.rs: pass -> [missing] (J0)
  • [ui] tests/ui/issues/issue-51022.rs: pass -> [missing] (J0)
  • [ui] tests/ui/mismatched_types/array-len-is-closure.rs: [missing] -> pass (J0)
  • [ui] tests/ui/traits/next-solver/normalize/deeply-normalize-env-in-compare-impl-item.rs: [missing] -> pass (J0)
  • [ui] tests/ui/traits/wrong-multiple-different-versions-of-a-crate.rs: [missing] -> pass (J0)
  • [ui] tests/ui/typeof/issue-100183.rs: pass -> [missing] (J0)
  • [ui] tests/ui/typeof/issue-29184.rs: pass -> [missing] (J0)
  • [ui] tests/ui/typeof/issue-42060.rs: pass -> [missing] (J0)
  • [ui] tests/ui/typeof/type_mismatch.rs: pass -> [missing] (J0)
  • [rustdoc] tests/rustdoc/const-generics/const-param-type-references-generics.rs: [missing] -> pass (J2)
  • [ui] tests/rustdoc-ui/issues/ice-typeof-102986.rs: pass -> [missing] (J2)

Additionally, 56 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard f392ed53ca3884c96430f2a283ffffa836b204f5 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. aarch64-apple: 8011.5s -> 10004.6s (+24.9%)
  2. x86_64-gnu-gcc: 2857.3s -> 3447.0s (+20.6%)
  3. x86_64-gnu-miri: 4091.8s -> 4829.7s (+18.0%)
  4. i686-gnu-1: 6987.5s -> 8117.3s (+16.2%)
  5. i686-gnu-2: 5342.9s -> 6203.4s (+16.1%)
  6. dist-x86_64-apple: 6734.7s -> 7796.9s (+15.8%)
  7. pr-check-1: 1716.1s -> 1961.9s (+14.3%)
  8. x86_64-rust-for-linux: 2643.5s -> 3015.8s (+14.1%)
  9. x86_64-gnu-llvm-20: 2420.1s -> 2757.1s (+13.9%)
  10. x86_64-msvc-1: 9740.5s -> 8565.6s (-12.1%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (f392ed5): comparison URL.

Overall result: ❌ regressions - please read the text below

Our benchmarks found a performance regression caused by this PR.
This might be an actual regression, but it can also be just noise.

Next Steps:

  • If the regression was expected or you think it can be justified,
    please write a comment with sufficient written justification, and add
    @rustbot label: +perf-regression-triaged to it, to mark the regression as triaged.
  • If you think that you know of a way to resolve the regression, try to create
    a new PR with a fix for the regression.
  • If you do not understand the regression or you think that it is just noise,
    you can ask the @rust-lang/wg-compiler-performance working group for help (members of this group
    were already notified of this PR).

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
1.7% [0.1%, 2.6%] 4
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

Results (primary -2.6%, secondary -1.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
2.4% [2.4%, 2.4%] 1
Improvements ✅
(primary)
-2.6% [-2.7%, -2.4%] 2
Improvements ✅
(secondary)
-2.7% [-3.3%, -2.1%] 2
All ❌✅ (primary) -2.6% [-2.7%, -2.4%] 2

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 470.335s -> 472.637s (0.49%)
Artifact size: 386.93 MiB -> 386.94 MiB (0.00%)

@rustbot rustbot added the perf-regression Performance regression. label Nov 27, 2025
@matthiaskrgr
Copy link
Member Author

@lcnr looks like #149345 changed some next-solver benchmarks? 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-tidy Area: The tidy tool merged-by-bors This PR was explicitly merged by bors. perf-regression Performance regression. rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-clippy Relevant to the Clippy team. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output. T-rustfmt Relevant to the rustfmt team, which will review and decide on the PR/issue. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants