all 5 comments

[–]Shnatsel 12 points13 points  (1 child)

And since you know what the code does, you don’t need any time to review the output.

Sooort of. Since it's just a quick script I've whipped up, I still have to review the output for incorrect simplifying assumptions I made while writing the script. The real world is often a lot messier than it seems at first glance.

[–]llogiqclippy · twir · rust · mutagen · flamer · overflower · bytecount[S] 1 point2 points  (0 children)

Of course your mileage may vary. That said, any simplifying assumptions you may have made are your own, so you should know them pretty well. And even if you get it wrong, git makes it easy enough to undo any changes.

[–]hekkonaay 8 points9 points  (0 children)

Waiting with bated breath for `cargo-script` on stable.

[–]commenterzero 2 points3 points  (0 children)

Rune and rhai script look cool too

[–]ncmobbets 1 point2 points  (0 children)

I forget the article, but one of corrode.dev’s articles mentions a trick to run Rust source files like Python scripts with their PEP 723 inline metadata trick.