Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 14 commits
- 8 files changed
- 4 contributors
Commits on May 14, 2016
Commits on Jun 1, 2016
-
Pool buffers for quoted strings and byte slices
This reduces allocations when writing multiple quoted strings or byte slices, by reusing bytes.Buffers, giving a nice little speed up. name old time/op new time/op delta EncodeKeyval-8 635ns ± 2% 593ns ± 0% -6.52% (p=0.008 n=5+5) name old alloc/op new alloc/op delta EncodeKeyval-8 176B ± 0% 64B ± 0% -63.64% (p=0.008 n=5+5) name old allocs/op new allocs/op delta EncodeKeyval-8 5.00 ± 0% 4.00 ± 0% -20.00% (p=0.008 n=5+5)
-
-
Merge pull request #2 from nuss-justin/buffer-pool
Pool buffers for quoted strings and byte slices
Commits on Nov 14, 2016
-
-
-
- for parse/write/parse check, change second parse to parse the write of the parsed value instead of the original input encode: - invalidKeyRune: treat utf8.RuneError as invalid rune - add invalidKey, invalidKeyString funcs - checks len(key) == 0, invalidKeyRune, and utf8.Valid - needsQuotedValueRune: if value contains utf8.RuneError quote the value. a literal k=\ufffd encodes to k=\"\\ufffd\" - writeStringValue, writeBytesValue: quote any invalid utf8 string - the above two changes fix the "reserialized data does not match" error found during fuzz testing decode: - reject invalidKey as parse error jsonstring: - remove "&& size == 1" when checking for rune decode error fuzz testing output: - .quoted: "0=\"\xbd\x00\"" - .output: panic: reserialized data does not match: "0=\"\\ufffd\\u0000\"\n" "0=\"�\\u0000\"\n"
Commits on Nov 15, 2016
-
-
Merge pull request #4 from judwhite/feature/fuzz
Fuzz fix, quote invalid UTF-8 values
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.2.0...v0.3.0