Currently the article states:
For instance, RFC 8259 mentions that a design goal of JSON was to be "a subset of JavaScript", but it's actually not. Specifically, JSON allows the Unicode line terminators U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR to appear unescaped. But JavaScript specifies that strings cannot contains line terminators (ECMA-262 - 7.8.4 String Literals), and line terminators include... U+2028 and U+2029 (7.3 Line Terminators). The single fact that these two characters are allowed without escape in JSON strings while they are not in JavaScript implies that JSON is not a subset of JavaScript, despite the JSON design goals.
However, there was a proposal to fix this issue in ES2019 that was adopted.
Indeed, the ES2019 section on Line Terminators no longer restricts all line terminators, but only and . Here's the highlighted diff:
See also: Subsume JSON a.k.a. JSON ⊂ ECMAScript · V8
At the moment, the article only mentions PRs intended for fixing typos, but would a PR adding an update below the aformentioned paragraph be desirable/accepted?
Currently the article states:
However, there was a proposal to fix this issue in ES2019 that was adopted.
Indeed, the ES2019 section on Line Terminators no longer restricts all line terminators, but only and . Here's the highlighted diff:
See also: Subsume JSON a.k.a. JSON ⊂ ECMAScript · V8
At the moment, the article only mentions PRs intended for fixing typos, but would a PR adding an update below the aformentioned paragraph be desirable/accepted?