You might want to checkout rust-script which essentially does the same but also lets you use it as a hashbang line to make executable rust scripts. And works with cargo/can install deps.
There is also an RFC for this feature.
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Credits
You might want to checkout rust-script which essentially does the same but also lets you use it as a hashbang line to make executable rust scripts. And works with cargo/can install deps.
There is also an RFC for this feature.
That's pretty cool, but terrifying as well. Can't wait for somebody to go a step further and start writing proc macros (call it rusht
) to replace bash scripts with rust scripts. Actually, now that I think about it, not so terrifying. They can probably be debugged better, could be safer (unless someone starts publishing malicious proc macros), allow dependencies to be added to compose better scripts without relying on they system's package manager, and so much more.
Thank for sharing rust-script which is basically what I made but written in Rust and seems to store the binary in another directory when the binary is exexuted.
Is the RFC trying to introduce a command cargo script
to run single rust scripts?
Is there a reason you're not just doing "cargo run"?
I admire the willingness to share your work, but this is easier to do with a disposable one-liner at the prompt that you can repeat with an up arrow and a carriage return, if needed.
Sure, this script would be perfect for something like a cron job, but that would raise quite a few more questions as to why you would complie on a fixed schedule.
I can think of a few edge-cases where this script would be useful, but it just seems like it adds extra steps where extra steps might not be needed.
It could be done with a one liner in the terminal but adding arguments when running the binary will be in the middle of the command, not at the end of the command.
Also the usecase for me is for sample scripts I have. This makes it easy to compile, run and delete the binary.
If it's useful to you, that is great.
Will rustc not just overwrite the old binary? If you are just doing a cleanup task, that's cool. If nuking the last binary is important, then just do it first:
rm ./code; rustc ./code.rs -o ./code; ./code -mah args
Or a makefile / justfile would be good too.
I put those on each directory and do just run
to pick up the thing I was working on quickly.