Heinz N. Gies
Heinz N. Gies
Sorry for the late reply, this got buried in a bunch of other notification :) yes that's quite possible, the big difference between `serde` and `simd-json` in this regard is...
Ja making parse_i8 generically parsing strings comes with some problems, one alternative would be looking at the Map deserializer, perhaps it's possible to hook into that bit? https://github.com/simd-lite/simd-json/blob/main/src/serde/de.rs#L295 A cutsoim...
yes that makes perfect sense :+1: I didn't knew that existed :) good call!
Ja that was the goal, seems not to work as hoped when run in a real non AVX2/SSE4.2 compatible computer - sadly something at least I can't test. But as...
That's a really good idea, I never thought about that!
That's a great idea!
Not done but the relevant traits now live in `value-trait`
That's a bit complicated to answer - one of those "it depends" situations 😠simd gets 'better' for medium and larger files, for extremely small ones it's quite bad (i.e....
Also I noticed you're using `allow-non-simd` which will always be slower then serde as it disables all the simd optimisations
So I updated your benchmark a bit: ```rust #![allow(warnings)] use std::time::Instant; use serde::Deserialize; use simd_json_derive::Deserialize as SimdDeserialize; use serde_json; use simd_json; #[derive(Deserialize, SimdDeserialize)] struct Person { id: String, index: i32,...