encoding/json: behavior change for go1.14 for paragraph-sep and line-sep characters #36690
Comments
cc @mvdan |
This is a behavior change, but I didn't dig into how far back. Here is an easier way to see what's happening (https://play.golang.org/p/c-EBn0iL9DD):
This change was introduced here: 900ebcf I can't speak to its merits, but it's deliberate. |
FWIW, I prefer the new behavior. It was weird to me that Compact actually could grow the input text. As is now, there is no option to just return just JSONP valid JSON. The new defaults for the IMO that's fine and this issue can be closed or transitioned into a "document the behavior change" issue. |
It is a behavior change that will need to be listed in the release notes. |
The documentation wasn't touched in the CL because the docs never made any mention of character escaping. The new implementation matches the docs more closely. I agree that this should be in the release notes, though. Sending a CL. |
Change https://golang.org/cl/215817 mentions this issue: |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
https://play.golang.org/p/N5ODTRS_hCB
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: