encoding/json: reference to obselete RFC #22888
Closed
Milestone
Comments
You showed that we treat " I'd like to see a list of actual changes between the RFCs and then tests for those before we update the docs. |
Yes. RFC 4627 only allowed json text to be either object or array. RFC 7159 extended it's definition to include any value. Look at https://tools.ietf.org/html/rfc7159#page-15 Quoting that page, |
Sounds good. Feel free to send a change. |
Change https://golang.org/cl/79995 mentions this issue: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
https://tip.golang.org/pkg/encoding/json/ mentions RFC 4627. The RFC 4627 is obsolete by RFC 7159.
It looks like current implementation already confirms to RFC 7159. https://play.golang.org/p/lY-b3Ia13k
Should we update the rfc no in the docs?
The text was updated successfully, but these errors were encountered: