`fastgron`: 8.5s 2.2G resident

edit: Interestingly whilst doing this test, I piped the output into `fastgron -u` (39.5G resident) and `jq` rejected that. Will have to investigate further but it's a bit of a flaw if it can't rehydrate its own output into valid JSON.

I released fastgron v0.7.5 which contains fixed in string escaping. Could you please take another look?

Already commented on the github issue but will have another look, yep.

Sure, I saw it, thanks!

I fixed the semicolon bug, but of course correctness is more important.

Update for anyone following - 0.7.6 recreates my 800MB input JSON correctly after trip through `fastgron | fastgron -u` which is good work.

Thanks, it's a clear bug. I created a new issue for it: https://github.com/adamritter/fastgron/issues/19