rust-script VS rust

There is also rust-script[1] which runs "Rust files and expressions as scripts without any setup or compilation step." I wrote a data loader[2] in it for my Observable Framework project and have been very happy with its performance and overall ease including hot-reloading.

[1] https://rust-script.org

[2] https://observablehq.com/framework/loaders#routing

To address your concerns about non-trivial building process making Rust less suitable for small scripts : https://rust-script.org/ Work is actively being done. (not by me)

I started this as a little script made with rust-script, which took only a few hours to mock up, and then I was able to refactor the core logic into a much larger scriptable system over only about a day. And, Rust being Rust, it worked first time once I got it compiling! Also, I have to say, having a full-blown custom scripting engine just work is a novelty coming from web programming, and Rhai is a great choice if you need this sort of functionality in your own projects!

Use rust-script ! Instead of having a folder for each script, your script could be a single file, just like you would in python. Then you can put all the files in a single directory with a readme describing the functionality and use-case of each script.

In case you didn't notice in the Prior Art section, rust-script is the most actively maintained descendant of cargo-script (from which the cargo-eval crate is forked as well).

Someone even wrote https://rust-script.org/ to make that "shell scripting using Rust" use-case more convenient.

Is rust-script close enough?

That may have been more of the originator of the idea, but what I believe I had used was rust-script, looking into it more. That one isn't maintained.

If you want that, check out rust-script.

If you haven't dipped your touch-typing fingers into Rust yet, you really owe it to yourself. Rust is a modern programming language with features that make it suitable not only for systems programming -- its original purpose, but just about any other environment, too; there are frameworks that let your build web services, web applications including user interfaces, software for embedded devices, machine learning solutions, and of course, command-line tools. Since a custom GitHub Action is essentially a command-line tool that interacts with the system through files and environment variables, Rust is perfectly suited for that as well.

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.

The above Assert<{N % 2 == 1}> requires #![feature(generic_const_exprs)] and the nightly toolchain. See https://github.com/rust-lang/rust/issues/76560 for more info.