Always set synthetic position when deep cloning #1610
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.
Fixes an out of bounds crash found when compiling an internal project.
We weren't setting (-1, -1) as a position for non-leaf nodes when deep cloning them. As a result, we'd later use those positions to access a file's text that wasn't the file for the cloned node, so the positions were out of the file text's bounds.
The diff for some compiler tests increased because we now seem to omit a comma during emit, but I think this is a problem that can be addressed later.