Fuzzer: Fix tuple globals with non-constant children #6644
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.
We fixed two problems when creating globals: that tuples must be tuple.make, and
that global inits must be constant (which in rare cases they are not, if we run out of
input bytes in the middle). However, there can be a dependence between them that
we missed: the init might begin constant, but then if we need to fix it to be a
tuple.make we can introduce something non-constant there.
Reorder them so we handle the non-constant issue at the end, after any tuple.make
changes.