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
The AST is inconvenient; it has nesting of a forced hierarchy of particular types. In retrospect I think I'd prefer to construct rrd nodes directly. And now the tnode tree has positional information split off, I think these rrd nodes should serve well as an abstract representation of grammars for both transformation and for rendering to all outputs. In turn that makes the AST nodes redundant, and I think those can go.
So:
Move the rrd nodes out for general use;
Switch all outputs to the rrd nodes;
Have all outputs share the tree rewriting;
Construct the rrd nodes directly from parser actions;
Remove AST;
And perhaps:
6. Rename rrd nodes to AST
7. Rename tnode to rrd?
The text was updated successfully, but these errors were encountered:
The AST is inconvenient; it has nesting of a forced hierarchy of particular types. In retrospect I think I'd prefer to construct rrd nodes directly. And now the tnode tree has positional information split off, I think these rrd nodes should serve well as an abstract representation of grammars for both transformation and for rendering to all outputs. In turn that makes the AST nodes redundant, and I think those can go.
So:
And perhaps:
6. Rename rrd nodes to AST
7. Rename tnode to rrd?
The text was updated successfully, but these errors were encountered: