evcxr VS rust-script

In theory you should be able to create Rust notebooks (Jupyter notebook) using evcxr so maybe some AI, data analysis, prototyping make sense if you aim for good performance in final application (protype in evcxr and use notebook as reference to implement final application in Rust for speed and safety).

You should check out evcxr

I think you might like this project: https://github.com/google/evcxr . It brings the REPL workflow to Rust, so having fast iteration should not be an issue.

While not Elixir good, the evcxr python notebook plugin gets you 50% of the way there.

https://depth-first.com/articles/2020/09/21/interactive-rust...

https://github.com/google/evcxr

I've started liking evcxr (https://github.com/google/evcxr) for REPL. It's a little slow compared to other REPLs, but still good enough to be usable after initial load.

Would such a project make it possible to have a faster rust repl? We can use evcxr, but it definitely doesn't feel first-class.

I'm a long-time python developer and develop on the side in Rust for about as long as you, I also found myself familiar with the available datastructures and algorithms, as well as some FP-inspired syntax ( i.e. iterators instead of for loops ) . evcxr is reminiscent of ipython, it can even be integrated with jupyter notebook. And indeed I was surprised to find myself in such a familiar world. It's definitely something that more python developers should be aware of.

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?

So personally, I use: - bash for super super basic things - ifs and loops are pretty much off the table - Rust for anything more complex than that - I've had a good time using https://rust-script.org/ , it's got some really cool features, and a very Unix-y feel

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.