Just in case you will find this approach interesting, of course it’s just the question of personal dev experience

So if you haven’t any dynamically linking libraries or you don’t use any architecture specific crates, this should fairly easily. Like downloading toolchain for raspberry pi CPU and specifying another value for —target flag

For “kdl-rs”, a while ago I fixed one service which used this file format, and, in combination with miette, the error messages about invalid config were significantly better than serde + toml-rs by default. This thing really impressed me, as I lack some crate which would have much better errors

If I didn’t know about “Cargo”, line:

run cargo …

can be confusing, as there is no separations between field name and its value, at least for me. 🙃

Syntax highlighting can fix that, for sure.

Shouldn’t cross compiling be faster on your working machine? 🤔

Can you show a simple example when KDL is more expressive than TOML, in my opinion, default configuration file format in Rust?

I’ve spent so much time trying to make „buffered” and „concurrent” methods work for my types, and at the end came to conclusion that in simple cases, like mine, just do it yourself, and go further, business wants features, not elegant solutions

Yeah, so one of the solutions is just skipping it. Implementing things like „Future” or „futures::Stream” by yourself is tough, so if your end goal would just work with struct and method like „async fn next(&mut self) -> Result<T>”, I would suggest stick to it and not use Stream at all

As I remember you can use OpenSSL for that. In previous versions you could create RSA keys from p and q primes that you can deterministically choose, but in 3.0.0 this API is deprecated

Where do this helpful messages about invalid routes come from?