Fix decoding dynamic tuples and arrays with dynamic subtypes within tuples #440
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.
This PR fixes #429 . When decoding a tuple that is not static or an array with a subtype that is not static, the second value in the tuple returned by
decodeSignleType
is a pointer to the next element, NOT the length of the consumed element. So when decoding such an element within a tuple,consumed
should be set to consumedUnwrapped, NOT incremented by consumedUnwrapped.