Subject: Re: bug#20154: 25.0.50; json-encode-string is too slow for large strings

From: Dmitry Gutov <[email-masked]>
Date: Sun, 22 Mar 2015 20:26:37 +0200

On 03/22/2015 07:31 PM, Eli Zaretskii wrote:

> But when you've encoded them once, you only need to encode the
> additions, no?  If you can do this incrementally, the amount of work
> for each keystroke will be much smaller, I think.

It seems I've misunderstood you here, sorry.

The question of "why encode everything again" comes to down programmer's 
convenience, and not re-implementing parts of the JSON encoder.

At least until `json-encode' has a way to pass an already-encoded string 
verbatim, how else would you encode an alist like

       `(("file_data" .
          ((,full-path . (("contents" . ,file-contents)
                          ("filetypes" . ,file-types)))))
         ("filepath" . ,full-path)
         ("line_num" . ,line-num)
         ("column_num" . ,column-num))

to JSON, except by encoding everything again?