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 was initially specified as part of #14, but has been moved to a separate issue because it depends on #6, in that simplifying the built-in grammar down to a single non-terminal will make this change much easier to implement, and would erase a lot of the work if we did this change first.
Since !-evaluation depends on the non-terminal of the parse tree being evaluated, the parse-tree-to-expression conversion should do so as well, for consistency. Currently, any parse tree of the right shape that ends up in the final, evaluated parse tree can be converted to an expression and evaluated. This should be changed so that only parse trees with the built-in non-terminal can be evaluated; any other parse tree would produce a BLIMP_INVALID_PARSE_TREE error. This should not pose a burden, as the user must already control which parse trees end up in the final tree in order to ensure they have the right shape; additionally ensuring that they have the right non-terminal should be no harder.
The text was updated successfully, but these errors were encountered:
This was initially specified as part of #14, but has been moved to a separate issue because it depends on #6, in that simplifying the built-in grammar down to a single non-terminal will make this change much easier to implement, and would erase a lot of the work if we did this change first.
From the proposal from #14:
The text was updated successfully, but these errors were encountered: