evcxr VS iron.nvim

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.

For the record/list, there's also: - https://github.com/hkupty/iron.nvim and - https://github.com/jpalardy/vim-slime

For Codi, I migrated away to iron.nvim. Codi is really slick though :)

In the past, when I was using NeoVim more, I also used iron.nvim: https://github.com/hkupty/iron.nvim

I don't know about the remote part... but have you seen https://github.com/hkupty/iron.nvim?

I am using iron.nvim (https://github.com/hkupty/iron.nvim) as a REPL in julia and it kinda works. But tbh I am not a big fan of this kind of workflow that julia forces on you (but thats a different debate).

You can now toggle and interact with a GHCi repl within your editor. Or, if you prefer to use something like iron.nvim, you can now configure it to use haskell-tools.nvim to set up the repl command.