Properly Treat All Function Encodings as Tuples - #33
Merged
Merged
Conversation
In Ethereum's ABI encoding spec, all function calls are treated as tuple encodings. This was being inconsistently done in our interface, leading to errors encoding dynamic types. This patch fixes the issue and allows dynamic typing to encode correctly.
jflatow
approved these changes
Jun 10, 2020
This was referenced Jun 10, 2020
Open
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
2 participants
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.
In Ethereum's ABI encoding spec, all function calls are treated as tuple encodings. This was being inconsistently done in our interface, leading to errors encoding dynamic types. This patch fixes the issue and allows dynamic typing to encode correctly.