{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibzkpcw4ngc5uiwtm4euijuygtxygx2kpy3poaacrxdvxnokiooyy",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mfz42shpmii2"
  },
  "path": "/t/pre-rfc-deprecation-and-separation-of-the-dead-code-lint/24045#post_5",
  "publishedAt": "2026-03-01T15:01:29.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "expect(unused_data_structures)]` to expect that instead of `dead_code`. The exact list can be found [here"
  ],
  "textContent": "Apersoma:\n\n> For existing Rust programmers: The `dead_code` lint is now deprecated, each of the different items it covered have their own lints now so if you have a dead `struct` you'd use an `#expect(unused_data_structures)]` to expect that instead of `dead_code`. The exact list can be found [here. (The dead code lint docs would be updated to have a table with each thing covered and what now covers that).\n\nThis seems like a terrible user experience IMO. I would be strongly opposed to deprecating the existing `dead_code`. For one, because of churn. And for two, because it's extremely useful as a way to silence all dead code warnings. Which I often do during development. I don't want to have to go through and select the right lints to silence.",
  "title": "Pre-RFC: Deprecation and separation of the dead_code lint"
}