Consider specializing a subset for JSON about proposal-binary-ast

[ljharb]

Since object literals can contain both non-JSON-representable types, and because it can contain any arbitrary type that has a .toJSON method, what would be the advantage to trying to represent a “JSON-style” literal?

[Yoric]

For the moment, it's more of an intuition than anything else. But my intuition tells me that we should be able to make things faster and more efficient if we know that we're dealing with a very small subset of JavaScript that can only contain pure data, and in particular nothing unsafe (assuming that it doesn't throw a SyntaxError).

[ljharb]

That sounds nice, but I’m not sure how those things can be statically known.

[dead-claudia]

@Yoric Take a look at BSON (used in MongoDB) and CBOR (used in some memory-sensitive cases). They both are very highly inspired by JSON, up to and including a default schema-less representation and a relatively small-ish set of primitive types.