querify getting fake doc items

[mejrs]

No description provided.

[mejrs]

@bors try @rust-timer queue

[rust-bors]

☀️ Try build successful (CI)
Build commit: f21c600 (f21c6005f028eabfec72893ab56022b3891a81f0)
Base parent: 34baba5 (34baba5394fcbda4cba7b7c1964a6db421c77c91)

[rust-timer]

Finished benchmarking commit (f21c600): comparison URL.

Overall result: ✅ improvements - no action needed

Benchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf.

@bors rollup=never rustc-perf
@rustbot label: -S-waiting-on-perf -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)	0.2%	[0.1%, 0.3%]	2
Improvements ✅ (primary)	-0.7%	[-2.6%, -0.1%]	27
Improvements ✅ (secondary)	-1.4%	[-2.6%, -0.3%]	52
All ❌✅ (primary)	-0.7%	[-2.6%, -0.1%]	27

Max RSS (memory usage)

Results (primary 0.3%, secondary 0.9%)

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

	mean	range	count
Regressions ❌ (primary)	1.3%	[0.7%, 1.9%]	4
Regressions ❌ (secondary)	1.7%	[0.7%, 2.5%]	4
Improvements ✅ (primary)	-1.1%	[-1.5%, -0.5%]	3
Improvements ✅ (secondary)	-2.0%	[-2.0%, -2.0%]	1
All ❌✅ (primary)	0.3%	[-1.5%, 1.9%]	7

Cycles

Results (primary 2.0%, secondary -6.5%)

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

	mean	range	count
Regressions ❌ (primary)	2.0%	[2.0%, 2.0%]	1
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-6.5%	[-30.8%, -1.6%]	7
All ❌✅ (primary)	2.0%	[2.0%, 2.0%]	1

Binary size

This perf run didn't have relevant results for this metric.

Bootstrap: 455.832s -> 457.539s (0.37%)
Artifact size: 399.69 MiB -> 399.63 MiB (-0.02%)

[rustbot]

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

[rustbot]

r? @dingxiangfei2009

rustbot has assigned @dingxiangfei2009.
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

Why was this reviewer chosen?

The reviewer was selected based on:

• Owners of files modified in this PR: compiler
• compiler expanded to 75 candidates
• Random selection from 16 candidates

[camelid]

r? @camelid