Get rid of clean::Deprecation

[jyn514]

This brings the size of item.deprecation from 56 to 16 bytes. Helps with #79103 and #76382, in the same vein as #79957.

r? @GuillaumeGomez

[jyn514]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion

[bors]

⌛ Trying commit 7d45243 with merge b63794ab1dbc729a6d5a8620d0fd64a6afb4d10f...

[bors]

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

[rust-timer]

Queued b63794ab1dbc729a6d5a8620d0fd64a6afb4d10f with parent 8b3ee82, future comparison URL.

[rust-timer]

Finished benchmarking try commit (b63794ab1dbc729a6d5a8620d0fd64a6afb4d10f): comparison url.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying rollup- to bors.

Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up.

@bors rollup=never
@rustbot modify labels: +S-waiting-on-review -S-waiting-on-perf

[jyn514]

The changes in instruction counts are marginal, but -.5% on max-rss. I think this is worth landing just for the cleanup honestly.

[GuillaumeGomez]

Just the fact that it removes code makes it worth it. 😄

@bors: r+

[bors]

📌 Commit 7d45243 has been approved by GuillaumeGomez

[bors]

⌛ Testing commit 7d45243 with merge 0298b3901dd66b407dfb15352c06e83bea0eecb4...

[bors]

💔 Test failed - checks-actions

[rust-log-analyzer]

Your PR failed (pretty log, raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log.

I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact @rust-lang/infra. (Feature Requests)

[jyn514]

The dist-x86_64-apple job failed, but there's no build log to see why :/ @rust-lang/infra do you know what's going wrong here?

@bors retry

[bors]

⌛ Testing commit 7d45243 with merge 90f4b52...

[bors]

☀️ Test successful - checks-actions
Approved by: GuillaumeGomez
Pushing 90f4b52 to master...

[pietroalbini]

do you know what's going wrong here?

Not having logs usually happens when the machine is disconnected from the network / crashes. My guess is that's probably https://www.githubstatus.com/incidents/3jr0nb7zjpbm.