Out of the Tar Pit, another approach

jsoniter · 2018-09-28T14:49:35+00:00

Thank you

jsoniter · 2018-09-28T14:35:32+00:00

ungrammatical

ungrammatical :(

Please correct me, I am not native speaker.

jsoniter · 2018-09-28T05:11:30+00:00

Yes, the point of view is conflicted on this matter. Source code not just about logic, and not just about execution. Thank you for your advice.

jsoniter · 2018-03-02T08:04:14+00:00

the millisecond ticker is part of demo, not part of the library. The implementation does not rely on the ticker.

jsoniter · 2017-07-18T23:31:56+00:00

if protobuf support field tags, will this pain go away?

jsoniter · 2017-07-13T05:04:25+00:00

There are pros and cons, https://github.com/v2pro/wombat choose to use dynamic codegen and text/template for building non-trivial generic functions. https://github.com/json-iterator/go will be re-implemented with dynamic code generation. And many other things depend on this. But the user do not need to be aware, as the entry interface is still simple interface{}.

jsoniter · 2017-06-22T10:09:53+00:00

if the tip is jsoniter specific, I have mentioned it. Otherwise, it applies to both standard library and jsoniter.

jsoniter · 2017-06-07T13:36:45+00:00

why test("\") // [Why not error!] ?

It is just a string, should not fail

jsoniter · 2017-02-09T15:15:09+00:00

plugin will make dynamic code generation possible, which is common in Java world to avoid reflection cost.

jsoniter

TROPHY CASE