simd-json-derive icon indicating copy to clipboard operation
simd-json-derive copied to clipboard

high performance Serialize and Deserialize derives

Results 9 simd-json-derive issues
Sort by recently updated
recently updated
newest added

add `#[serde(default)]` as supported modifier

I'm trying to take advantage of simd_json's support of serde compatible structs. However, I'm finding that there is no performance gains when using `simd_json::serde::from_str` or the slice equivalent. Having seen...

although I really do think there should be a discussion about the safety of the parsing code, why is parse fallible, and why we parse the array, without having the...

bitfield is supposed to return the parsed struct. Instead it just returns input array (bytes). (`fn from_bytes([u8; 1]) -> Self`) Ref: https://docs.rs/modular-bitfield/latest/modular_bitfield/#generated-implementations **To reproduce:** ```rust #![allow(dead_code)] use std::io::Cursor; use binrw::BinRead;...

Hello @Licenser! Thank you for sharing your excellent work. I'm delighted to see that this crate shaves off about half the run time when parsing a huge binary file into...

enhancement

Easier than I expected! I still have to try it out and see if it works well before merging, but at least it compiles.

If we have a type that includes another datatype and so on, we still have a write command for each type even so at compile time we would know the...

enhancement

Is it possible to reuse the storage that was allocated for the Tape Vec? Based on my digging it doesn't look to be possible in the current state. If I...

How big of a task is it to skip over these fields when deriving Serialize? Ex: ```rs struct Ye { a: u16, _b: u8, c: u32, } ``` should produce...