Allen

能否提供复现问题的demo或者输入的json串协助进行问题定位和分析？

Hi, can you put your test code here or on [playground](https://play.golang.org/) for us to reproduce the bug?

@jilieryuyi 自定义Decoder或Encoder， 可以参考extension_tests/decoder_test.go >>> ```go func Test_customize_type_decoder(t *testing.T) { t.Skip() jsoniter.RegisterTypeDecoderFunc("time.Time", func(ptr unsafe.Pointer, iter *jsoniter.Iterator) { t, err := time.ParseInLocation("2006-01-02 15:04:05", iter.ReadString(), time.UTC) if err != nil { iter.Error =...

Can you upload example and benchmarks? Thanks

Is there any progress on this issue? @coreyfarrell Are you still working on the new json raw type?

@Houlton I didn't reproduce your issue. 

go test -test.benchmem -bench "(JsonParser|fastjson|GJson)" ./benchmark/ -benchtime 5s -v goos: windows goarch: amd64 pkg: benchmarks BenchmarkJsonParserLarge BenchmarkJsonParserLarge-4 88914 70391 ns/op 0 B/op 0 allocs/op BenchmarkJsonParserMedium BenchmarkJsonParserMedium-4 568888 10794 ns/op 0...

@phuslu Could you pls show your test case so we can analyse the performance bottleneck?

@nikolas7892 Has your problem been solved, if not, can you provide the implementation?

Can your provide the reproduce payload?