fix: revert '+' syntax optimize && add growth check limit for 'random_recursive_mutation' #44
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.
for issue #42, I revert '+' syntax optimize
for issue #43, Grammar-Mutator has to rely on AST to work, in the case of TOKEN conflicts, grammar parsing may fail. at the same time, Grammar-Mutator will try to retain data for nodes that fail to parse. If the depth of the syntax tree is large and grammar parsing errors occur, it may cause
random_recursive_mutation
to be mutated each time. the data size exceeds 1024 bytes, thus falling intodo-while
. I added an failed limit for this.