A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/tc39/proposal-record-tuple/issues/330 below:

JSON.parseImmutable as a separate companion proposal · Issue #330 · tc39/proposal-record-tuple · GitHub

This repository was archived by the owner on Apr 15, 2025. It is now read-only.

This repository was archived by the owner on Apr 15, 2025. It is now read-only.

JSON.parseImmutable as a separate companion proposal #330

Description

JSON.parseImmutable seems like it can be expressed as an option given to JSON.parse since it's otherwise identical as far as I'm aware. I see that in #74 it was originally imagined this way but quickly rejected. But couldn't we take an options bag in place of the reviver and branch on its type?

This kind of question is why I'm still a little uneasy about whether JSON.parseImmutable should be pursued as a follow-on proposal or not.

ljharb, GitHub30 and lin72h

Metadata Metadata

Assignees

No one assigned

Development

No branches or pull requests Issue actions

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4