{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiaozbrsxiolurx7o4xox4we57n2ngcf6qkjf7ksojykleecdo6n2y",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mk4csc4afxr2"
  },
  "path": "/t/pre-rfc-cargo-package-should-include-fewer-files-by-default/24188#post_4",
  "publishedAt": "2026-04-22T18:29:16.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "kpreid:\n\n> Most packages’ tests do not take up significant amounts of disk space (or have any non-code files at all). Keeping tests, when they are cheap, is valuable for “wait, did this published package ever work as intended? If so, on which Rust versions?” kinds of investigations. I also think that it would be valuable if `cargo publish` verification _ran tests_ to reduce the chances of publishing a broken-as-published package — all the more so if the default file exclusion rules were stricter.\n\nCertainly it would be bad if we can't use crater any more because most things end up with broken tests.",
  "title": "[Pre-RFC] `cargo package` should include fewer files by default"
}