Closed theonlynexus closed 2 years ago
This issue has been automatically marked as stale because it has not had activity for 365 days. It will be closed if no further activity occurs within 56 days. Thank you for your contributions.
No plans to merge?
As mentioned in the conversation thread, I am closing the PR because in retrospect it seems rather non-sensical. Not sure what was going through my mind when I opened it.
Thanks for following up. It's potentially a safe change, as UTF-8 is a superset of ASCII.
Ideally the API would change to require the caller to specify an Encoding
when passing a string
. We are careful about breaking APIs though.
In page 9 of the RFC, there is the following paragraph:
"8.1. Character Encoding JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32. The default encoding is UTF-8, and JSON texts that are encoded in UTF-8 are interoperable[...]"