On Fri, Aug 9, 2019 at 8:53 AM Jonathan Hall <fli...@flimzy.com> wrote: > > Can you say more? Better in which way?
Better in the way that it wouldn't change existing code. Also, I think the use cases for existing and proposed json encoders/decoders are different enough to justify a separate implementation. A wihle ago with similar concerns you described, I wrote a separate json encoder/decoder using the existing ones to deal with large json files. The purpose was to stream json input/output, and direct json manipulation in memory. I ended up using that only for cases where I expect large json data, and use the std encoder/decoder for small json processing like config files, or API calls with known structures. > > > On Friday, August 9, 2019 at 4:46:19 PM UTC+2, burak serdar wrote: >> >> >> Instead of modifying the existing Encoder/Decoder, wouldn't it be >> better to do this as a separate encoder/decoder? >> >> >> >> >> > >> > >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "golang-nuts" group. >> > To unsubscribe from this group and stop receiving emails from it, send an >> > email to golan...@googlegroups.com. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msgid/golang-nuts/9b081989-0ffa-40a1-8d6b-f56833e7b749%40googlegroups.com. > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/cc2b65c1-4abc-4309-b0c8-b311456873ee%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAMV2RqpN_PufK3icB9DnS6pMSEoUCQZGbo5b0jMJTSM%3Dcp3n-Q%40mail.gmail.com.
