Hacker GitHub

← All repos

tc39/proposal-json-superset

View on GitHub ↗ ★ 123 archived

Proposal to make all JSON text valid ECMA-262

6 mentions on Hacker News by 6 people: 0 stories, 6 comments · first 2018-02-03 · latest 2023-04-23

Mentions per year 6 mentions · busiest year 2019 (3)
20082026
AllStoriesComments NewestTopOldest
  1. …I like the name.... ;-D So all JSON is valid (modern) JavaScript. [1] Is RON valid Rust? [1] https://github.com/tc39/proposal-json-superset
    comment by ronyeh · 2023-04-23 · in Ron: Rusty Object Notation
  2. The article leads with an incorrect statement. JSON is now a subset of JavaScript: https://github.com/tc39/proposal-json-superset
    comment by spankalee · 2019-12-28 · in Unintuitive JSON Parsing
  3. JSON is a syntactic subset of Javascript in ES2019 [1]. https://github.com/tc39/proposal-json-superset
    comment by ZephyrP · 2019-09-18 · in The cost of parsing JSON
  4. That bit of incompatibility will be going away when this proposal is implemented, however: https://github.com/tc39/proposal-json-superset
    comment by empyrical · 2019-02-21 · in Simdjson – Parsing Gigabytes of JSON per Second
  5. …goal of JSON was to be "a subset of JavaScript", but it's actually not. Actually, it's really close https://github.com/tc39/proposal-json-superset This is a stage 3 proposal likely to make it to the next version of the spec. At which point…
    comment by inglor · 2018-04-22 · in Parsing JSON is a Minefield
  6. …that can't be represented in ES object literals. There's a proposal in Stage 3 to fix that though: https://github.com/tc39/proposal-json-superset
    comment by epmatsw · 2018-02-03 · in ECMAScript 2018: final feature set