fast-float-rust VS json

I'd like the mention my own refactoring of fast-float-rust to remove nearly all unsafe code for merging into Rust core library which left the performance identical to the previous implementation.

JSON is an interesting example, since the syntax of valid floats is slightly different than what Rust expects. Luckily, I'm the author of a minimal, and am also the author of a PR to bring this to fast-float-rust.

[4] https://github.com/aldanor/fast-float-rust/

It seems also dependent on the processor: https://github.com/aldanor/fast-float-rust/#intel-i7-4771

I've already done that (just pushed it - here).

Oh wow. So serde_json doesn't roundtrip floats by default, it uses some imprecise faster algorithm https://github.com/serde-rs/json/issues/707

Good thing there's msgpack I guess.

tokio / hyper / toml / serde / serde_json / json5 / console

Serde JSON, an extension of the serde crate that enables the serialization and deserialization of Rust structs.

To serialize and deserialize data, we'll employ the popular serde crate along with serde_json. This will allow us to easily convert between Rust types and JSON when working with API requests and responses. For async operations we'll use the Rust futures crate.

From the Cargo.toml file above, we can see that the Perseus version at the time of publication is 0.4.2 and has the following dependencies that are common to both the engine side (server-side) and client side of a Perseus application: sycamore, serde, and serde_json.

serde_json

Number parsing uses a fairly naive but uses a lossless algorithm in musli-json. In serde_json they use a fork of lexical I haven't wrapped my head around. I wanted something simple to start with.

Your best best would be to use an enum. Either your own or something like the one from serde_json depending on what you are trying to do.

Don't do that if you care about memory usage. In your toy program, I wouldn't be surprised if memory usage was a lot better if you used Box instead. (even if it doesn't look like it, you can handle almost all the use cases of serde_json::Value with it, often not much less convenient)