inline tuple_fields

[lcnr]

more #93505 fun, after this i have no idea what might be causing the perf impact.

[rust-highfive]

r? @davidtwco

(rust-highfive has picked a reviewer for you, use r? to override)

[lcnr]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit 423600d with merge 21b401a310360c8e5cfecbcd5cb790662722386d...

[bors]

☀️ Try build successful - checks-actions
Build commit: 21b401a310360c8e5cfecbcd5cb790662722386d (21b401a310360c8e5cfecbcd5cb790662722386d)

[rust-timer]

Queued 21b401a310360c8e5cfecbcd5cb790662722386d with parent b751124, future comparison URL.

[rust-timer]

Finished benchmarking commit (21b401a310360c8e5cfecbcd5cb790662722386d): comparison url.

Summary: This benchmark run did not return any relevant results. 4 results were found to be statistically significant but too small to be relevant.

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR led to changes in compiler perf.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf -perf-regression

[lcnr]

seems like a slight improvement

[michaelwoerister]

Seems reasonable in any case.
@bors r+

[bors]

📌 Commit 423600d has been approved by michaelwoerister

[bors]

⌛ Testing commit 423600d with merge be52b4a...

[bors]

☀️ Test successful - checks-actions
Approved by: michaelwoerister
Pushing be52b4a to master...

[rust-timer]

Finished benchmarking commit (be52b4a): comparison url.

Summary: This benchmark run did not return any relevant results.

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

@rustbot label: -perf-regression