Skip to content

Rollup of 2 pull requests#151875

Merged
rust-bors[bot] merged 6 commits intorust-lang:mainfrom
JonathanBrouwer:rollup-OPCJQtC
Jan 31, 2026
Merged

Rollup of 2 pull requests#151875
rust-bors[bot] merged 6 commits intorust-lang:mainfrom
JonathanBrouwer:rollup-OPCJQtC

Conversation

@JonathanBrouwer
Copy link
Contributor

Successful merges:

r? @ghost

Create a similar rollup

fee1-dead and others added 6 commits January 30, 2026 15:52
…k, r=oli-obk

constify `Iterator`, take IV

Like its predecessors (rust-lang#92433, rust-lang#102225, rust-lang#106541), this PR allows one to make `Iterator` implementations `const`, and thus enables the ability to have `for` loops in `const` contexts. I've also included constifying `Option as IntoIterator`, `option::IntoIter as Iterator` as a minimal dogfooding example.

But unlike its predecessors, it uses a new attribute (not unsound anymore!) that prevents any `Iterator` extension methods from being called. This is intentionally made minimal for an initial approval, the fun stuff like `.fold`, `Range as Iterator` could be done later.

cc @rust-lang/wg-const-eval, cc @oli-obk to review the compiler parts

cc rust-lang#92476
…bank

resolve: Remove `force` parameter from `resolve_ident_in_scope`

`force == true` is used for turning `Determinacy::Undetermined` into `Determinacy::Determined` during error recovery.
It's only needed in two places:
- `resolve_macro_or_delegation_path` - the normal case
- `resolve_path_with_ribs` - obscure case, only when resolving visibilities and only for improving diagnostics in `tests\ui\resolve\visibility-indeterminate.rs`, I'm not actually sure if we should keep it

In other cases `Determinacy::Undetermined` is just ignored or can be propagated.
@rust-bors rust-bors bot added the rollup A PR which is a rollup label Jan 30, 2026
@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) A-rustc-dev-guide Area: rustc-dev-guide S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. 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. labels Jan 30, 2026
@JonathanBrouwer
Copy link
Contributor Author

@bors r+ rollup=never p=5

@rust-bors
Copy link
Contributor

rust-bors bot commented Jan 30, 2026

📌 Commit 4884de4 has been approved by JonathanBrouwer

It is now in the queue for this repository.

@rust-bors rust-bors bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jan 30, 2026
@rust-bors

This comment has been minimized.

@rust-bors rust-bors bot added merged-by-bors This PR was explicitly merged by bors. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Jan 31, 2026
@rust-bors
Copy link
Contributor

rust-bors bot commented Jan 31, 2026

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 7m 58s
Pushing 44e34e1 to main...

@rust-bors rust-bors bot merged commit 44e34e1 into rust-lang:main Jan 31, 2026
12 checks passed
@rustbot rustbot added this to the 1.95.0 milestone Jan 31, 2026
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#151281 constify Iterator, take IV 0d294e3ea36549239308de8f87a948758c5baa81 (link)
#151873 resolve: Remove force parameter from `resolve_ident_in_sc… b48181ce5758b5f0fe9c2b5ce7f51fe480cb15ac (link)

previous master: a293cc4af8

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 a293cc4 (parent) -> 44e34e1 (this PR)

Test differences

Show 694 test diffs

Stage 1

  • [ui] tests/ui/traits/const-traits/partial/attr-gate.rs: [missing] -> pass (J2)
  • [ui] tests/ui/traits/const-traits/partial/no-const-callers.rs: [missing] -> pass (J2)
  • iter::test_const_iter: [missing] -> pass (J3)

Stage 2

  • iter::test_const_iter: [missing] -> pass (J0)
  • [ui] tests/ui/traits/const-traits/partial/attr-gate.rs: [missing] -> pass (J1)
  • [ui] tests/ui/traits/const-traits/partial/no-const-callers.rs: [missing] -> pass (J1)

Additionally, 688 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 44e34e1ac6d7e69b40856cf1403d3da145319c30 --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. dist-apple-various: 3516.5s -> 5651.8s (+60.7%)
  2. pr-check-1: 1678.6s -> 2064.0s (+23.0%)
  3. x86_64-gnu-miri: 4004.9s -> 4893.4s (+22.2%)
  4. pr-check-2: 2281.9s -> 2625.4s (+15.1%)
  5. i686-gnu-2: 5363.5s -> 6084.3s (+13.4%)
  6. x86_64-gnu-tools: 3403.6s -> 3818.7s (+12.2%)
  7. dist-x86_64-apple: 7783.0s -> 6841.3s (-12.1%)
  8. aarch64-apple: 11438.4s -> 10098.7s (-11.7%)
  9. x86_64-gnu-llvm-21-2: 5208.5s -> 5781.2s (+11.0%)
  10. aarch64-msvc-2: 5725.9s -> 6336.6s (+10.7%)
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 (44e34e1): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

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)
2.2% [2.2%, 2.2%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (primary -1.3%, secondary 3.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)
3.0% [2.9%, 3.2%] 2
Improvements ✅
(primary)
-1.3% [-1.8%, -0.8%] 2
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) -1.3% [-1.8%, -0.8%] 2

Cycles

Results (primary 2.8%, secondary 3.9%)

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

mean range count
Regressions ❌
(primary)
2.8% [2.8%, 2.8%] 1
Regressions ❌
(secondary)
3.9% [3.0%, 4.3%] 3
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 2.8% [2.8%, 2.8%] 1

Binary size

Results (primary 0.1%, secondary 0.1%)

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

mean range count
Regressions ❌
(primary)
0.1% [0.0%, 0.1%] 18
Regressions ❌
(secondary)
0.1% [0.0%, 0.1%] 42
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.1% [0.0%, 0.1%] 18

Bootstrap: 473.657s -> 474.436s (0.16%)
Artifact size: 397.74 MiB -> 397.79 MiB (0.01%)

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

Labels

A-attributes Area: Attributes (`#[…]`, `#![…]`) A-rustc-dev-guide Area: rustc-dev-guide merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants