Zach Collier

I guess it's not json.org, but it links to this page: https://www.crockford.com/mckeeman.html

For a drop-in replacement, I believe the easy fix is to flip the default value of `jsonLastValueWins` to true so the default behavior matches the existing behavior. So Go's default...

Jordan, you've always done fantastic work on JSON5. Thank you for reading this proposal. Perhaps JSON5 doesn't need to make the distinction? Instead, implementations MUST support `unique`, and SHOULD support...

Sorry, my response was poorly written. This is better: Implementations MUST support duplicate behavior `unique`. Implementations MAY support additional duplicate behaviors. Perhaps "non-standard" is a better word here than "undefined"....

Any more thoughts? I suspect the next step is to draft an example by adding a few sentences about duplicate behavior to the spec section `3 Objects`. Having a concrete...

> https://262.ecma-international.org/5.1/#sec-C Ah! Thank you! >become non-compliant Totally, and that's a great concern. We've seen a "change" like this before: The [JSON RFC 7159](https://datatracker.ietf.org/doc/html/rfc7159#section-8.1) allowed UTF-8, UTF-16, or UTF-32. The...

> It is a SyntaxError if [strict mode code](https://262.ecma-international.org/5.1/#sec-10.1.1) contains an ObjectLiteral with more than one definition of any data property ([11.1.5](https://262.ecma-international.org/5.1/#sec-11.1.5)). Perhaps this changed with ES6? Do you know...

Would the following address your suggestions? 1. Support unary. 2. Support emoji characters. 3. Option for Unicode markup ("U+"). 4. Support surrogate characters. I think unary is interesting. Since internally...

This is partially fixed with preceding padding. See example: https://convert.zamicol.com/?in=090e5c14c2237ecbc906879d50ae1b12&inAlph=0123456789abcdef&outAlph=0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz&lpad=true It is not fixed for succeeding padding as in https://tools.ietf.org/html/rfc4648#section-4.

I think JSON spec concerns are addressed on the other issue and that's probably the better place for discussion on Coze's relationship to the JSON spec: https://github.com/Cyphrme/Coze/issues/10#issuecomment-1501047859