Rename toU64(), toU256() for consistency with other functions #119
+410
−410
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.
Description
In slow & fast VM, there are toU64(v uint8) and toU256(v uint8). But in the Solidity implementation, there are functions with the same name, but their argument type is uint64. This makes developer confused and could make bugs. So renamed go functions to
byteToU64()
andbyteToU256()
to prevent confusion.