Heinz N. Gies
Heinz N. Gies
This is the whole code that compiles for me, but the inout seems to be invalid as the funk function crashes: ```rust use binrw::BinRead; use simd_json_derive::Serialize; use std::io::Cursor; pub fn...
nice glad we got that working and it's really cool to hear this could cut the execution time in half :D
if they're all the same do they need to be different sturcts? (could you give examples of how CustmField1 and 2 are looking?)
Ah I see, one way to deal with that is making a macro for it something like (the syntax might be slightly off): ```rust macro_rules! string_type { ( $x:ident )...
that would be something that needs flattening and be implemented in the upper level, so you'd either need to hand roll the entire serializer to not use the wrapper
Thank you :)! I'll rename the issue if you don't mind to better capture that support or const generics would be nice.
Puh that's quite hard to answer without a lot of context. There are a few general things to consider, and in some situations, simd_json isn't always faster than serve. 1)...
I agree, definetly worth considering and revisiting! I pulled this in it's own issue so it's nut buried in a completed PR :)
a few startingpoints: 1) the tape is (assuming no bugs) guaranteed to be valid JSON, all validation from formating (numbers, strings etc) and structure (correct k/v of objects, correct nesting...
I think that's something the `binrw` people have to answer, since if the struct only shows `bytes` there is nothing the derive can do about that.