privacy: Fix privacy lints in RPITITs

[petrochenkov]

Visit RPITITs and report private_interfaces, private_bounds and exported_private_dependencies in them (these are regular, non-deprecation lints).
New hard errors are not reported, #146470 is for hard errors.
So this PR doesn't contain any breakage or language changes.

[rustbot]

r? @eholk

rustbot has assigned @eholk.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[rustbot]

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

[petrochenkov]

ping @eholk, it's been 2 weeks.

[eholk]

Sorry about my delay here. Looking now!

[eholk]

@bors r+

[rust-bors]

📌 Commit 7c9d149 has been approved by eholk

It is now in the queue for this repository.

[rust-bors]

☀️ Test successful - CI
Approved by: eholk
Duration: 3h 36m 5s
Pushing ef2657c to main...

[github-actions]

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 35a31ba (parent) -> ef2657c (this PR)

Test differences

Show 8 test diffs

Stage 1

• [ui] tests/ui/privacy/missing-mir-priv-bounds-2.rs: [missing] -> pass (J0)
• [ui] tests/ui/privacy/missing-mir-priv-bounds-3.rs: [missing] -> pass (J0)
• [ui] tests/ui/privacy/missing-mir-priv-bounds.rs: [missing] -> pass (J0)

Stage 2

• [ui] tests/ui/privacy/missing-mir-priv-bounds-2.rs: [missing] -> pass (J1)
• [ui] tests/ui/privacy/missing-mir-priv-bounds-3.rs: [missing] -> pass (J1)
• [ui] tests/ui/privacy/missing-mir-priv-bounds.rs: [missing] -> pass (J1)

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

Job group index

• J0: x86_64-gnu-llvm-20-3, x86_64-gnu-llvm-21-3
• J1: aarch64-apple, aarch64-gnu, aarch64-gnu-llvm-20-1, aarch64-msvc-1, arm-android, armhf-gnu, dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-1, i686-msvc-1, test-various, x86_64-gnu, x86_64-gnu-debug, x86_64-gnu-gcc, x86_64-gnu-llvm-20, x86_64-gnu-llvm-20-2, x86_64-gnu-llvm-21-2, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-1, x86_64-msvc-1

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard ef2657cbaf6885b71e5ffd277ffe72a2616c0a7c --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: 8964.1s -> 12499.0s (+39.4%)
2. x86_64-gnu-gcc: 3407.2s -> 4154.3s (+21.9%)
3. dist-aarch64-apple: 6754.1s -> 8111.3s (+20.1%)
4. pr-check-1: 1611.1s -> 1879.3s (+16.6%)
5. x86_64-gnu-miri: 4172.3s -> 4826.5s (+15.7%)
6. x86_64-rust-for-linux: 2704.6s -> 3082.4s (+14.0%)
7. i686-gnu-2: 5251.1s -> 5965.8s (+13.6%)
8. test-various: 6582.7s -> 7468.7s (+13.5%)
9. x86_64-gnu-tools: 3304.8s -> 3731.5s (+12.9%)
10. dist-x86_64-apple: 9031.0s -> 7986.5s (-11.6%)

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]

Finished benchmarking commit (ef2657c): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

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

Max RSS (memory usage)

Results (primary 0.1%)

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

	mean	range	count
Regressions ❌ (primary)	1.2%	[0.6%, 1.8%]	2
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-2.0%	[-2.0%, -2.0%]	1
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.1%	[-2.0%, 1.8%]	3

Cycles

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

Binary size

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

Bootstrap: 476.214s -> 545.612s (14.57%)
Artifact size: 397.88 MiB -> 397.86 MiB (-0.00%)