argparse VS json

The most feature-rich C++ CLI library is CLI11. Other popular choices include Boost.ProgramOptions, argparse, cxxopts and others.

It was noted by u/k1lk1 that it wasn't entirely obvious what the benefits of this library are, so I'll compare arg_router to argparse, with a simple but common example.

You're looking for an argument parsing library. There are tons of these. My favorite is the excelent Rust crate called clap. For C++, the argparse library is a decent option.

p-ranav/argparse - A single-file header-only C++11 library for parsing command line arguments.

I tried to make the code modular as much as possible. However, in main.cpp I have used the argparse and termcolor along with the main function. As Sam, pointed out, it would be a good idea to move them to a separate file and import them in main.cpp.

argparse is another good one. Templated (delicious), tested, AND has conan and debian package deployment.

argparse ➜ repository

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)