cargo-outdated VS cargo-script

cargo-outdated

I've tried to use cargo-outdated like so:

Thanks to cargo and the community, project maintenance is straightforward in rust. You'll need to install cargo-outdated and cargo-audit:

Use the automated tools to assist you in the maintenance of your projects: rustfmt, clippy, cargo update, cargo outdated and cargo-audit.

I'd add cargo-outdated for checking for outdated dependencies. cargo-tree is also useful, but that's built into cargo itself for some time already.

Some combination of cargo-outdated and cargo-msrv could probably do this in a slightly more manual fashion.

So it merges functionality of cargo-outdated and cargo-audit?

Accept BTC, all credit card * $1 .unwrap() - wallhack through Err * $2 .ok() - invisibility cheat for unused Result warning * $5 .unwrap_unchecked() - advanced wallhack, never fall out of map from panic For script console, just $10.

You can also use cargo script. After installing it you can just do

I think there are some projects in this area, eg, https://github.com/DanielKeep/cargo-script. For my personal scripts, I have a single Cargo.toml for a busy-box style multiplexed binary: https://github.com/matklad/config/blob/f0259ca8a3755f2e62a3bf472c2514fd6cb891ff/tool/src/main.rs#L16.

O seems that this does already exist: https://github.com/DanielKeep/cargo-script

You don't have to set up a project if you use cargo-script

Take a look at cargo script. That should/could do what you want

when I first started using rust, I knew python a lot better so I would write scripts with python. at this point though, I write a lot more rust than python these days, so I'll write pretty much everything with rust. cargo-script is a useful tool for this, as well as the self-compiling script: https://neosmart.net/blog/2020/self-compiling-rust-code/

Another option is cargo-script, which lets you run self contained rust files.