SyntheticBird

Found the solution! Add the following to `settings.json`: ```json "lsp": { "rust-analyzer": { "initialization_options": { "check": { "allTargets": false } } } } ```

> This fails to compile as the functions are private, they could be made pub(crate) My bad. I didn't see heed/env.rs using `fixed_bytes()`. Why not replace: ```rust // Add leeway...

lmao nah no need to resolve conflict for that

I would like to add that some methods in `/json_rpc` endpoint does return epee binary responses, or a mix of json response with some of its field containing raw binary....

I prefer cuprated. the confusion with cup-rated is funny, the community is already used to it, and people will easily find out what the d means. It could be a...

> Q: Should `cuprate` directly handle X.509 certificates and keys (and thus HTTPS/SSL)? I don't understand the meaning of *directly handle*d ? If the question is *Should cuprate support user...

> Would something like criterion be helpful instead of making something custom? Last time we wanted to test out `read_from` visitor pattern vs `to_le_bytes`, we used criterion and I find...

> Using criterion means benchmarking will be limited to cargo bench [...] AFAIA, It uses `cargo bench` indeed. If providing a binary is a necessity, then `criterion` we should forget....

then `criterion` we should use

I was thinking about the similarities between `tokio` blocking threadpool and `rayon` one. Someone [on reddit](https://reddit.com/r/rust/comments/xec77k/rayon_or_tokio_for_heavy_filesystem_io_workloads/) described the difference between the two. Despite tokio being supposedly more suitable for our...