It might be worth considering adding simd-json to the TechEmpower benchmarks:

https://github.com/TechEmpower/FrameworkBenchmarks/blob/cfbbf5d11143c96851620eb1aeaf3c2893e862c9/frameworks/Rust/actix/src/main.rs#L23

To make this really worthwhile #121 would be good.

suggested by @pickfire

Hi! I am very new to Rust, so I apologize if this ends up being a naive question.

So, for my robot motion optimization application, I have created an objective function and gradient function in the required format using closures, but the closure types are FnMut’s rather than Fn’s. This leads to the compiler complaining since the OpEn library forces the objective and gradient functions to be F

flatc has rich set of arguments https://google.github.io/flatbuffers/flatbuffers_guide_using_schema_compiler.html

I saw you implement the basic set that works just fine, but for example I'd love to modify the --filename-suffix, but cannot findout how?

Help would be much appreciated!

Expand the available list of system metrics. Around 10-15 new metrics (the most useful we can think of) is a good start.

Current enum behavior

#[derive(Debug, PartialEq, DekuRead, DekuWrite)]
#[deku(id_type = "u8")]
enum Packet {
    #[deku(id = "0x00")]
    Zero,
    #[deku(id = "0x01")]
    One,
    #[deku(id = "0x02")]
    Two,
    #[deku(id = "0x03")]
    Three,
    #[deku(id = "0x04")]
    Four,
}

attribute inherit which would inherit the id from the value already assigned.

Apparently align_to is spec'd such that you can just fail to do the conversion, and so MIRI for example choose to just fail and return the starting slice every time.

That's crap, and we need to implement a "by hand" version that doesn't fail so that MIRI can't try to give us the run-around.

Is your feature request related to a problem? Please describe.
The crate needs better documentation. Things like the top level of the crate are not documented. It also needs some doctest type stuff in the examples as part of the documentation.