{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreia2u5wtxhzr7ij2njhzb7f6gqgidb34aj4kvwghmxwgg3n73nq32q",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mgeh3zkkojo2"
  },
  "path": "/t/alternative-to-cargo-new-templates-examples-as-build-target-templates/24047#post_14",
  "publishedAt": "2026-03-05T22:23:11.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "crates.io"
  ],
  "textContent": "epage:\n\n> So your proposal is for there to be crates that exist but aren't part of the package or workspace that get bundled in the package? I feel like that could be confusing.\n\nI mean, is it any different to tests, benchmarks, or examples as-is? `docs.rs` will include snippets of code from examples in documentation, but examples aren't themselves published to crates.io, so there is definitely precedent here.\n\nepage:\n\n> Please re-read my original post. Making `cargo new` additive is a major part of this idea.\n\nSorry I think I worded that badly, what I meant was for an MVP on templates we don't need to consider the additive functionality yet, that can be added after there's a mechanism for templates. Whereas, I don't think you can make `cargo new` additive without templates (aside from just creating empty files I guess?)",
  "title": "Alternative to `cargo new` templates: examples as build-target templates"
}