Construct Expr directly from ParseStream #268
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Generalize
build_tree
so that we can more easily construct tree types other thanGreenNode
. Use this to constructExpr
directly fromParseStream
rather than constructing both GreenNode and SyntaxNode along the way.Fix a bunch of type instabilities in the
Expr
conversion code along the way.With these changes, parsing all of Base to
Expr
is sped up by about 35% overall and allocations reduced by around 50%. (Parsing toExpr
is now comparable with parsing toSyntaxNode
.)