- 15 Jan, 2019 2 commits
-
-
Eric Myhre authored
ISTM that since we're talking about raw data more so than "objects" in any kind of Alan-Kay/sending-messages/OOP sort of way, calling it "struct" is more accurate communication. (It's also a lot less likely to be confusing when mentioned in the same context as javascript, since "object" and "map" tend to be collisiony terms there; whereas "struct" just doensn't really have any prior associations in that community as far as I know.) Signed-off-by: Eric Myhre <hash@exultant.us>
-
Eric Myhre authored
All of these struct definitions are horrifying similar in construction to the same-named definitions in the typesystem package: simply ever instance of a Type pointer is instead a TypeName string. Despite being unattractive, this is correct: since typesystem can have pointers and cycles, and typedeclaration can't, this is what we end up with. Signed-off-by: Eric Myhre <hash@exultant.us>
-