Add limit for expression nodes in parsed ASTs. - #2166
Merged
Conversation
copybara-service
Bot
force-pushed
the
test_954705811
branch
2 times, most recently
from
July 27, 2026 21:58
4893e46 to
192e38d
Compare
This is mainly to prevent misbehaving macros from generating an AST that is much larger than expected (not directly proportional to source length). PiperOrigin-RevId: 954860770
copybara-service
Bot
force-pushed
the
test_954705811
branch
from
July 27, 2026 22:28
192e38d to
02b617c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add limit for expression nodes in parsed ASTs.
This is mainly to prevent misbehaving macros from generating an
AST that is much larger than expected (not directly proportional to
source length).