evcxr VS bincode

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.

Ermm... actually I meant something like this: playground, but then I realized it's basically (de)serialization, and I just found that we already have a crate for that: bincode.

One, figure out the bincode format (documented here: https://github.com/bincode-org/bincode/blob/trunk/docs/spec.md) and write your own parser. Maybe a one-off that specifically only handles this one data structure would be fairly straightforward.

Step 1: The Deserialize type requests data from the Deserializer with one of the deserialize_type methods. This gives it an opportunity to provide certain metadata about the type: structs provide a list of fields, enums provide a list of variants, tuples provide a length, etc. Some data formats (notably bincode) require this metadata to drive deserializing, as the wire format is not self-describing. Crucially, the Deserialize type also provides a visitor that is capable of receiving the requested data from the Deserializer.

Alternatively, give Bincode a try.

If you can use std, have you had a look at the crate [bincode](https://crates.io/crates/bincode)? If you can't use std, I've found the crate [bincode-nostd](https://crates.io/crates/bincode-no-std) which is old but maybe you can find something similar and more recent?

Like separate instructions? I was thinking if a instruction have unknown length I make sure I have some kind of header field that tells the data length of the instruction so receiver knows when next instruction starts. And I was planning on using Bincode with serde to serialize and dezerialize like structs and stuff.

Isn't this essentially bincode?

This is similar in practice to using abi_stable, and end-users will still receive compiled files, but your plugins will be sandboxed and a single build will work on all platforms. The downside is that it's a bit more work because WebAssembly's support for passing complex data types between the host and the WebAssembly code is in the preliminary stages, so you need to do something like using Serde to encode your data into something like Bincode or MessagePack (or JSON and friends) to hand it off between the host and the plugin.

The network manager handles serializing it into a binary format (using the bincode crate https://crates.io/crates/bincode), sending it out to other clients on a separate IO thread etc. I'm not exactly sure how bincode handles the serializations, but it allows me to automatically derive ways for a struct (in this case, Snapshot) to be serialized and desterilized to/from raw bytes which can be sent/received over the network.

I've built type-specific hacks to avoid this which produce up to 50% runtime improvements. Latest one is in this PR: https://github.com/bincode-org/bincode/pull/337. The standard library should provide a way to sidestep the copy through a pointer. Useful BufRead/BufWrite traits would be a good start.