You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This can be a simple racket program that reads in the current batch of expaded data and produces something in a reduced grammar. This reduced grammar will have a direct interpretation as an algebraic type in our language.
Proposal from slack:
(1) I propose that we emphasize "expr" and squish away all top-level / module-related forms to the following:
(2) we keep all the constructors of "expr" in the same order as the Racket docs, and that determines their tags, starting with 0
(3) for our own purposes we introduce the tags VARREF, F1, F2, F3 above, which are not part of the original grammar
(4) we build-in a notion of list fields in our ASTs, e.g. (list Sym). Worst-case they could be new, packed cons-list datatypes, but we can do better if we bake them in.
(5) by convention we strip all occurrences of #% prefixes in tags
The text was updated successfully, but these errors were encountered:
This can be a simple racket program that reads in the current batch of expaded data and produces something in a reduced grammar. This reduced grammar will have a direct interpretation as an algebraic type in our language.
Proposal from slack:
(1) I propose that we emphasize "expr" and squish away all top-level / module-related forms to the following:
(2) we keep all the constructors of "expr" in the same order as the Racket docs, and that determines their tags, starting with 0
(3) for our own purposes we introduce the tags VARREF, F1, F2, F3 above, which are not part of the original grammar
(4) we build-in a notion of list fields in our ASTs, e.g.
(list Sym)
. Worst-case they could be new, packed cons-list datatypes, but we can do better if we bake them in.(5) by convention we strip all occurrences of
#%
prefixes in tagsThe text was updated successfully, but these errors were encountered: