Re: [Json] JSON and int64s - any change in current best practice since I-JSON

[Joe Hildebrand <[e-mail]>]

Regardless, this would be a hard fork of JSON, with a new name -- I just started a git repo called "ESON", for instance.  Like YAML, one of the goals might be that all well-formed JSON is well-formed ESON, and would produce the same thing that you expected from your local equivalent of JSON.parse.

I'm not sure why other platforms couldn't parse this:

```eson
[
  // Always generates a bigint
  1n,
]
```

into a single element array containing their local bigint type?

— 
Joe Hildebrand

> On Jan 17, 2024, at 11:41 AM, Carsten Bormann <[e-mail]> wrote:
> 
> On 2024-01-17, at 17:28, Joe Hildebrand <[e-mail]> wrote:
>> 
>> The approach that seems right to me is to make it explicit; bigint's get suffixed with 'n', and there is not automatic promotion to break existing code.
> 
> This creates a fork of JSON that is only useful with JavaScript?
> 
> (To use it with other platforms, you’d need to do exactly the “automatic promotions to break existing code”.)
> 
> Grüße, Carsten
>