`cargo new --script`

[epage]

Problem

Overall, cargo script has been intended to be lightweight enough to not need cargo new support.

When we add support for workspaces, things will shift including

• Opting in to workspace discovery (the proposed package.workspace = true)
• Auto-inheriting

Proposed Solution

cargo new --script foo.rs to create

#!/usr/bin/env cargo
---
[package]
edition = "<current>"
---

fn main() {}

and when in a workspace:

#!/usr/bin/env cargo
---
[package]
edition = "<current>"
workspace = true
... any `workspace.package` fields
---

fn main() {}

Notes

Is --script the right name?

[epage]

This is more intended for when someone puts forward an RFC for workspace support for Cargo Script but I wanted a place to record my thoughts.