Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AST scan to establish a non-conflicting expression ID for pruning #703

Merged
merged 2 commits into from
May 15, 2023

Conversation

TristonianJones
Copy link
Collaborator

Thanks @charithe for the repro cases. I've done a non-recursive scan, but the tradeoff is memory. Open to suggestions.

Closes #699

@TristonianJones TristonianJones requested a review from l46kok May 12, 2023 01:15
interpreter/prune.go Outdated Show resolved Hide resolved
interpreter/prune.go Outdated Show resolved Hide resolved
interpreter/prune.go Outdated Show resolved Hide resolved
@TristonianJones
Copy link
Collaborator Author

PTAL

@TristonianJones TristonianJones merged commit a465d93 into google:master May 15, 2023
@TristonianJones TristonianJones deleted the prune-id-fix branch May 15, 2023 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PruneAST overwrites existing nodes and produces an invalid AST
2 participants