{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreic2vvv2rcydv4r7pcuztcu37n7km74ahz7bowafct3umd6wnqpdjm",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkbre6vxjdu2"
  },
  "path": "/t/pre-rfc-cargo-package-should-include-fewer-files-by-default/24188?page=2#post_24",
  "publishedAt": "2026-04-24T23:10:41.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "blobby",
    "exclude"
  ],
  "textContent": "kpreid:\n\n> Tangential to the rest of the thread, but I think that this should be considered poor practice.\n\nI disagree. We use `include_bytes!` pretty extensively in RustCrypto by encoding KATs into a custom binary format, including the resulting blob, and parsing it at compile time (see the blobby crate).\n\nWhat do you propose to use instead? Keep thousands of KAT lines as part of source code? Or use file IO to read KATs at runtime? We want to have compact tests, keep the compile time checks (e.g. that the blobs have expected format) and to be able to execute tests on `no_std` targets (with some minor tweaking).\n\nNow, I agree that excluding only blobs and thus breaking tests is not correct and should be discouraged. For example, in `cmac` we exclude both \"large\" blob and module which uses it.",
  "title": "[Pre-RFC] `cargo package` should include fewer files by default"
}