Michael Färber

Ok, I went forward and incorporated your tests for `until` in c8190bb. Thanks again!

Thanks for your example. I can see that there are lots of decimal numbers in the input, and preserving these perfectly as strings may slow down processing. I will however...

Ok, I have looked a bit at your test file. I found the following: Reading the file with `$(JQ) 'empty' < citylots.json` takes about 9.3s for `jq` and 10.9s for...

I made another quick experiment: I mapped all numbers contained in `serde_json` values to constant 0 in the output `jaq` value. This way, `$(JQ) 'empty' < citylots.json` takes **10.4s**. That...

Yes. One crazy idea: Use [`simd_json`](https://github.com/simd-lite/simd-json) for high-performance parsing. I also stumbled over [`ijson`](https://github.com/Diggsey/ijson). I just tried to integrated `simd_json` into `jaq`, but failed, because I use [`serde_json::Deserializer::into_iter`](https://docs.rs/serde_json/latest/serde_json/struct.Deserializer.html#method.into_iter), but [`simd_json::Deserializer`](https://docs.rs/simd-json/latest/simd_json/struct.Deserializer.html)...

> This is true, but if I understand correctly, the main problem is the flexibility of serde_json. Yes, but if the JSON parser is much faster, then even with the...

I found that after all, serde_json seems to provide the flexibility that we need ... mostly. I just have not figured out yet how to deal with arbitrary precision numbers.

Don't forget the "mostly" part. ;)

Oh, that sounds like a deficiency in the parser! I will unfortunately not get around to diagnose it right now, as I'm going on holiday for several weeks tomorrow. On...

I just implemented `-f`. Thanks for your suggestion. I was also able reproduce your performance issue; parsing your filter (and giving the error about `gsub`) takes 27 seconds here. It...