Naming bikeshed: "immutable"

[ljharb]

I think the word "immutable" is sufficiently overloaded that it'd cause confusion to use it.

All primitives are immutable, but so are frozen objects without internal slots that have no "non-immutable object" properties.

I'd love to gather suggestions of alternate names that can convey "produces Records and Tuples instead of Objects and Arrays" in a way that doesn't have nuances and edge cases. _{(I'll make my own suggestions in independent comments, as I come up with them, so they can be emoji-reacted to individually)}

[hax]

I raised the similar issue in original proposal: tc39/proposal-record-tuple#327

Here are the names I suggested: parsePrimitive or parseAsPrimitive

[ljharb]

“Primitive” includes things that JSON doesn’t - symbols and undefined, in particular.

[hax]

@ljharb Yeah, and JSON also don't include bigints and special float values (NaN, ±Infinity). But I think it's still correct to say it only generate primitives?

[OmarCastro]

Well, there is another option, JSON.parseConst. Since the value cannot be changed, it is effectively constant.

[ljharb]

const in JS only has the connotation of "constant reference", which isn't the same as "immutable".

[chimericdream]

What about something like JSON.parseStatic or JSON.parseFinal?

[ljharb]

what's dynamic or non-final about the existing parsing?