I concur with the proposal that records and tuples serialize to JSON via JSON.stringify as object and array. It strikes me that there may be value in providing support for going in the other direction, to somehow parameterize JSON.parse to yield a structure consisting of records and tuples. Obviously, this could be implemented in user land with the existing JSON.parse and some tree crawling and type conversion logic, but supporting it directly would be a good deal more efficient. Since many use cases for parsing JSON (actually, I'd speculate a majority of them) neither need nor want the parsed result to be mutable this could be a win.
rricard, papb and littledanmormahr
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